Think Micro-services, but don’t think Micro and don’t think Services
Micro-services, although undeniably the flavor of the season, is a much-misunderstood architecture concept. The confusion, in my opinion is due to the term itself. A more appropriate term, for instance, something along the lines of ‘Independent Business Vertical Component’ would have been relevant to the architecture, though been less appealing or glamorous.
The word ‘Micro’ forces people to think too ‘granular’, often compromising independence of micro-services and causing unnecessary overheads, whereas the word 'Services' steer people toward technical implementation, rather than thinking about ‘business’ services.
In my recent blog, I have discussed the misconceptions surrounding micro-services and it's impact on the way they are used.
Please read my blog here - https://www.lntinfotech.com/blogs/think-micro-services-but-dont-think-micro-and-dont-think-services/
Let me know what you think.
You summed up very well "The primary objective of the micro-services architecture is to achieve ‘independence’ of services and ‘speed of delivery’. However, this is often achieved at the expense of operational ‘simplicity’, so it is very important to take a call on where you will use micro-services architecture."
Digital Transformation Leader
5 年Great article. If you have a few minutes, we should chat about the practical use in insurance.