When should one consider microservice kind of architecture?

1.	When should one consider microservice kind of architecture?
Answer» There are two cases. If you ALREADY have a monolith application and it grows to an extent where there are problems in scaling or we are not able to REUTILIZE the components/modules/services across different projects/platforms and there is a need to do so. As well as at the same time implementing new FEATURES is painful and more error-prone and it is difficult to scale further. For new applications where implementation has not started yet started, we can THINK of a business case to be efficiently implemented, which can be easily maintainable, testable and scalable in the future and might be used across other projects/products/platforms at the same time.

Answer»

There are two cases.

If you ALREADY have a monolith application and it grows to an extent where there are problems in scaling or we are not able to REUTILIZE the components/modules/services across different projects/platforms and there is a need to do so. As well as at the same time implementing new FEATURES is painful and more error-prone and it is difficult to scale further.
For new applications where implementation has not started yet started, we can THINK of a business case to be efficiently implemented, which can be easily maintainable, testable and scalable in the future and might be used across other projects/products/platforms at the same time.

Discussion