For what type of application microservices architecture is not good choice. Microservices architecture is become overhead in term of performance and application management.
Microservices architecture is suitable for what type of application?
Share
Linda Gonzalez
I think one good example would be a customer acing application. Microservices work best in the cloud and this type needs to leverage the functionality in the cloud to be effective in orders, geo data and to integrate with other data sources. a banking mobile app might be a good example as the customer makes deposits or withdrawals, handling transactions across many customers. This can also make use of rapidly expanding as new customers make sue of the application. Easier to scale up without interfering with the rest of the application.
Guadalupe Gonzalez
In my opinion Microservices is suitable for large monolithic applications containing several modules with clear boundaries.
Tarek Mahran
I think Microservices is best choice for converting complex legacy systems. If I will start new application from scratch and it’s requirements are clear I can go with SOA without complicating it with Microservices
balap
Microservices architecture is suitable for any dependent or independent monolithic applications/services
SudipSikdar
I think the applications , which can be broken into small , clear and discrete components .
These can be domain or business functional components. e.g. A shopping cart application.
Fahd Yousri
I agree with the opinion that microservices in most cases require a large complex monolithic application which is mature and has seperable functionalities that can be taken out to their own self contained modules.
Why go through the communication hassle microservices bring when the app is simple enough and can be easily developed as a monolith or an SOA.
If there is a capability within your monolithic stack which can be a common capability for other components. That’s should have been hosted centralised and managed separately. Examples like an Identity management capability. You can make that as managed services with microservices architecture.
Also if you break your e2e customer journey as various independent flows. Then those can be developed as microservices. Any new applications is best suitable for that architecture rather than a big monolithic web application.