Skip to main content

Why Microservices?


I have a few tidbits about why to use microservices and why it makes sense to create few microservices as a side project and learn from the same. A lot has been said on why you should use microservices in the internet, that said, I look at it from a practical point of view and give you a very basic idea why we should use microservices and stop monoliths from becoming huge mountains of code in the future.

Advantages

  • Simpler codebase(s) - Multiple projects with simpler code to maintain.
  • Single responsibility - The microservice has a single responsibility and moves the developer from the mindset of developing everything together into separating multiple functional aspects into separate codebase.
  • Test coverage naturally increases - since the codebase becomes smaller, the code coverage increases and bugs are figured out earlier in the development lifecycle.
  • Readable codebase - Smaller equals precise and more readable and understandable. You have to understand this is different from simpler codebase because readability is a different aspect in itself.
  • More power to the developer - Developers can choose and implement their own languages or databases as long as the other teams can also chip and debug if necessary. So developers get more freedom to do what they want to do - code away!
  • Time taken to develop each microservice becomes less.
  • Change is less expensive to implement - As the services are small and easily readable and created within days and weeks, the changes to the same codebase becomes really less and better to make those changes and deploy them easily
  • Versioning becomes mainstream - incase of APIs, microservices make you follow versioning and it becomes the first nature of developers to implement versioning in their endpoints/REST api endpoints so that other microservices can still depend on the old endpoints. This helps in making versioning an explicit way of programming with microservices.
There are other reasons as well, but the above summarizes why you would need microservices and you can depend on the microservices to build your next project/sideproject. There are complexities as well in orchestrating the microservices, but I will work on them as a post at a later point of time. Meanwhile, you can practice and write your own microservices and play with them. Keep tuned for more posts.

You can follow me at Twitter, Facebook, LinkedIn and Website.

Comments

Post a Comment

Popular posts from this blog

Hackathons - Top 4 Reasons Why You Should Participate in Them

The story begins when I encountered a HBR post that works out a few metrics about how companies that have highly engaged employees, outperform those that doesn't. My brain started thinking passively about these metrics and how it can impact business in a larger sense and I started thinking how we can have better engaged workforce that benefits both the company and the employees themselves.

Then, one fine day, when I was driving my car mindlessly, not knowing how my minded drifted to the same topic, I was again deeply thinking about the ways that we could engage employees more in simpler ways and get them involved in more ideation and creation process. This, in my opinion, will create more avenues for the employees to gather real world problem and brainstorm its solutions and help them in their growth for their careers. I thought this could be a real problem that can be solved for the knowledge workers as a whole. Then suddenly there was a huge Volvo bus in front of me siding from…

B2B selling demystified like a Rockstar - Part One

I'm sure every person in the enterprise world knows the definition of b2b. B2B is short for “business to business.” It indicates sales made to other businesses, rather than sales to individuals. The latter is referred to as “business to consumer” sales, or b2c. This distinction makes the sales person think that b2b sales is very different from b2c. B2B requires a lot of interpersonal skills and lots of casestudies to get across to that particular influencer who needs to be convinced that your product/service is going to make a change to his organization. Is that right?

Before we get into the details of b2b selling, lets have a look at this particular statistic from Forrester Research.


"1 million B2B sales jobs in the U.S. will be obsolete by the year 2020." – Forrester Research What does this mean? And why is the b2b landscape changing a lot? Before we answer those questions, lets have a look at what b2b selling means.
How do you approach B2B
B2B selling is a step by process…
You will receive wonderful short stories written by him and inspirational articles once every month.