When is it worth adopting microservices architectures?
An application that requires more than five developers is certainly a good target for a microservices architecture since logical microservices help split the workforce into small, loosely coupled teams.
A high-traffic application with several time-consuming modules is also a good target for microservices architecture since it needs module-level performance optimizations.
Low-traffic applications that require just a small team of less than five people for their implementation are not a good target for a microservices architecture.
Deciding when to adopt microservices in all other situations that fall between the above extreme cases is not easy. In general, it requires a detailed analysis of costs and returns.
Considering costs, using a microservices architecture requires a development effort of about five times that of a usual monolithic application. We got this scale as an average on 7 total rewrites of monolithic...
