4 minutes to read read
Some time back as I remember, AWS was the biggest (and probably only leading) cloud provider. But with each gone day, Azure is increasing its product base in competition to AWS. Many of these products are inspired (don’t read as copy) originally from AWS. Also, in most of the Azure products, you will find a small asterisk hidden somewhere and cost is something which is more or less equal or expensive.
Despite all these facts, slowly and gradually with a pace approaching AWS and could takeover in a few years. Well, this seems to be a little too much from a developer without understanding of deeper market dynamics, but rather this is from the heart and trouble ship that I have faced, and probably many of the other developers facing. Alert, this post contains no code, but theory.
5 minutes to read read
With the advent of .Net Core, web Api have become more common. Apologies to my non-dotnet background friends, but with .net hands-on, its always inclined towards .net. Coming straight to the point, be it Mobile Apps, SPAs (Single Page Applications), micro-services or name whatever, you will see REST everywhere. In background of this post, old kishore kumar songs are running, so don’t offend a bit of nostalgia 😊.
But as in most cases, everyone is so busy in implementing the APIs, many of my friends don’t ever pay attention on how an API be named. Or rather, not an API but the endpoints and methods (hate to call them methods). Well, for an API the problem there is no standard as such, but rather some best practices, that should be followed ‘ideally’. Lets discuss them one by one. Most importantly, in this post shall be talking only on the API naming. I also had OpenApi in mind, but lets leave it for another post. So lets dive in.