Monoliths versus microservices is a very hot topic nowadays for programmers, engineers, and architects. The more we investigate these two approaches, the more we realize that when building an application from scratch, we need to select one of them from the beginning. I think that more or less everybody is interested in the microservices approach and everybody would like to use it. It is suitable to be used in a cloud-based scalable system, and it allows us to grow the system without taking too much care about the infrastructure we choose. But a rational investigation about the price to pay in terms of complexity, design, and maintenance gave us no real choice to make: the monolith wins. But, some months later... This is today's "to be or not to be" dilemma of software engineering.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.

This article is related to


microservices,distributed systems,monolith,modularization