Microserviço
De Basef
Revisão de 09h43min de 12 de janeiro de 2016 por Admin (discussão | contribs) (Criou página com 'http://highscalability.com/blog/2014/4/8/microservices-not-a-free-lunch.html https://rclayton.silvrback.com/failing-at-microservices https://www.quora.com/What-are-some-disa...')
http://highscalability.com/blog/2014/4/8/microservices-not-a-free-lunch.html
https://rclayton.silvrback.com/failing-at-microservices
https://www.quora.com/What-are-some-disadvantages-of-a-microservice-architecture
- Adds complexity to development due to its distributed nature.
- Adds overhead in terms of costs and operational complexity (build-test-deploy-run).
- Time to market may be hit adversely due to the distributed nature of the application.
- Monitoring the application in production deployment becomes a complex job, with multiple services.
- Service interface versioning needs to be managed for the multiple services.
- The operational challenges of Microservices architecture mean you need high quality DevOps and release automation skills as part of your development team.
- The asynchronous communication and distributed nature of the micro-services based system poses challenges for testing the system as a whole.
- Operational expenditure could be significantly higher depending on the complexity of the system.