(1) Developers must deal with the additional complexity of creating distributed systems.
Development tools (or IDEs) are oriented towards building traditional monolithic applications, and do not provide explicit support for developing distributed applications. Testing is more difficult. In the microservices architecture, there are many services, and each service is an independent business unit. The services mainly interact through interfaces. How to ensure the normal dependence is the main challenge for testing. Developers must implement communication mechanisms between services. When implementing use cases across multiple services, you need to face the difficulties of using distributed transaction management. Implementing use cases that span multiple services requires careful coordination between teams.
(2) Complexity of
deployment During deployment and management, the operation of a system composed of many different service types is relatively complex, which will require development, testing, and operation and maintenance personnel to have corresponding technical levels.
(3) Increasing memory consumption The
microservice architecture replaces a single application instance with multiple service instances. If each service runs in its own JVM, there will be as many instances as there are service instances. Memory overhead at runtime.
