In recent times, the term Microservices has gained immense popularity. It has found advocates in big players like Amazon, Netflix, NGINX to name a few. These companies have adopted this approach and have shared their first-hand experiences which are quite impressive. There is a growing inclination towards this approach. The Google trends for Microservices also corroborate the same.
So, what is Microservices? The term “Microservices” was coined to define an architectural style which proposes developing and maintaining an application as multiple small independent deployable units, specifically as services, that communicate via APIs.
There are no hard and fast rules as to how many individual services your application should be made of or how the breakdown should happen. Neither is there a specification as to the size of each unit. The only criterion is that each service should handle one responsibility and do it well. This is in unison with the core philosophy of UNIX “Make each program do one thing well”
To continue reading the full whitepaper register now
Latest posts by Revathi Chandrasekharan (see all)
- Splitting the Monolith into Microservices – Do’s and Don’ts - August 11, 2016