Microserviço

Microserviço

FROM IBM COURSE:

• ✓ Jones, T (2017). “So You’re Thinking of Decomposing Your Monolith into Microservices.”

• Richardson, C (2014). “Microservices: Decomposing Applications for Deployability and Scalability.”

• Daya, S. et al. (2015). “Microservices from Theory to Practice.” IBM Redbook (SG24-8275-00).

• Gehani, N (2017). “Want to develop great microservices? Reorganize your team.”

• Search on Iaas (this is a short article), PaaS, and SaaS

• Azraq, A. et al. (2017) “Essentials of Application Development on IBM Cloud.”

• Hay, D (2016). “4 Important Microservice Characteristics.”

• Montesi, F.; Weber, J. (2016). “Circuit Breakers, Discovery, and API Gateways in Microservices.”

• Torre, C. de la; Jones, M. (2017). “Communication in a microservice architecture.”

• Richardson, C. (2015). “Building Microservices: Using an API Gateway.”

• Montesi, F.; Weber, J. (2016). “Circuit Breakers, Discovery, and API Gateways in Microservices.”

• Peyrott, Sebastián (2015). “An Introduction to Microservices, Part 3: The Service Registry.”

• Huston, T (2017). “What is Microservices Architecture?”

• Kumar, M. (2016). “Microservices Architecture: What, When, and How.”

• Gehani, N (2017). “Want to develop great microservices? Reorganize your team.”

• Tikov, S (2015). “Don’t start with a monolith”.

• Microservices Not a free lunch! by Benjamin Wooton.

• Martin Fowler's article You must be this tall to use microservices

• Deployment Pipeline

• IBM DevOps for Dummies Version 3

• Managing Apps

• IBM, Google and Lyft give microservices a ride on the Istio Service Mesh by Jason McGee

• Istio Platform

• Microservices from Theory to Practice: Creating Applications in IBM Bluemix Using the Microservices Approach SG24-8275-00

• Martin Fowler's article entitled MonolithFirst.

• Master data management

FROM UNIVERSITY RESEARCH:

• 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

• Team Communication Overhead - Microservice architecture reduce the team management complexity, but it is not able to diminish the need of team communication. They need to make sure update in one’s service is not breaking other functionality. We can found this problem in monolith architecture application too.
• Formal documentation overhead - Every individual running component app need to keep updated schemas and interface documents all the time. It helps other team using the service.
• Non uniform application - We can choose different technology stack for different component (plygot). It leads to problem of non uniform application design and architecture. It may can increase maintenance cost in long run.
• Dev Ops complexity - We need to have a mature Dev Ops team to handle the complexity involved in maintaining Microservice based application. Due to several moving parts of the application, it become complex and required a level of expertise.
• Increase Network communication - Independently running component interact with each other using network. Such system require reliable and fast network connections.
• Testing - Testing of such application is definitely harder in compare to monolith application.
• Production monitoring - Cost to monitor such application are higher. Unavailability of the right tools are also an issue to be considered.

• 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.

• Large numbers of microservices are difficult to orchestrate.
• Understanding, managing and testing dependencies is difficult.
• Introspection into what happens between microservices and testing across entire architectures is difficult. Think of microservices as many little monoliths. Services are separate and independent but the business logic is still hampered by a single address space.
• Large numbers of microservices are difficult to secure.
• Once requirements change, do you want a microservice for one new feature or re-write and add to an existing service. That is a difficult decision in an architecture with many microservices.