Let’s Go the microservice Way: Day 1

Background

You have written apps that work on your local, and you decide that let's go the microservice way to deploy your code. Very Good! But here starts the quest to find out all the extra details.

I found myself in a similar position, and in this series, I guide you on to my journey on how I finally brought up production-grade microservicevices from scratch.

Where to start

Before considering any design, the first thing that you must think of is the Requirement. You should not end up with a finished product that has all the good things but does not look like something that you wanted in the first place.

Roughly my requirements were:

• Single Point of access for all current and future microservices.
• Unified authentication mechanism for all services.
• Cloud-Native approach, but vendor-independent.
• Continuous Integration and Continuous Deployment. (CICD)
• Basic things like a Database and a Message Queue should come out of the box.
• Easy to scale up and down as and when needed.
• Security: No compromises at all.
• Cost-Effective.
• Easily promotable to production-grade if need be.

It's best to note these down somewhere nice. We would refer to these very frequently and almost always when in dilemma.

Final Notes

Think again and again about all your requirements. Changing them midway might be hard to accommodate, and might undo a lot of your work.

Once we have sealed it, let move on to some other stuff.