#rant that none asked for. I came across this whitepaper on testing micro services. I clicked on this link because I am writing microservices now but I am fairly new to microservices. I did a mistake that I have repeated 1593 times in the past. The said link was a resource by one of the big IT service providers.
While we love to have production-like environments for user testing, managing data and the test environments can present unique challenges. In today’s enterprises it is fairly common to have multiple test environments including staging, system / user testing environments and so on. These environments expect production-like features but only for specified users.
Why do I use GraphQL? Also, the case for not using GraphQL. You must have seen the previous post where I waxed eloquent about how I mess up my Rest APIs. There was no way I would be satisfied doing that to a single technology stack. Ergo, GraphQL. What is the need for GraphQL?
How not to design Rest services? This is not a theoritical introduction to Rest - there’s something called the ‘Great Internet’ for that. But, what I do want to (cautiously) write about is how I mess up the design principles carefully laid out by smarter people. Practice 1: Use verbs in resource names We typically use the following API names -
I have this annoying behaviour to force as many things as I can through the business layer. This can be a boon and bane at the same time. What do I mean by business layer? Let’s say I have an application running on AdonisJS. For every operation (CRUD) - I try to go through controllers/services Almost all of them through APIs when called from front-end Almost all of the operations through Lucid with exceptions through Database statements Use Tasks or equivalent for batches Everyone does this, why is it a point of discussion?
I was a MeteorJS fan. MeteorJS was an excellent tool to quickly create universal apps. I was not quite a professional developer back in the day (circa 2016-17) but I could recognize the power of Meteor in developing complex web applications that could potentially deployed for multiple devices. There was a time when I was flabbergasted as I, rather alarmingly, saw people moving from Meteor to different platforms.
Most of my coding a few years back consisted of the following actions - Type slowly Type (a lot of) mistakes Use spaces and tabs to format. Get confused about loops and add ad-hoc spaces and tabs Curse my typing skills and the soul who invented spaces and tabs While formatting code was also becoming an interim ‘thought provoker’, it was simply too much typing.