(1) The complexity of the application increases, and it is difficult to update and maintain.
A simple application will gradually become larger over time. Then the development team will face many problems. The main problem is that this application is too complicated, so that any single It is difficult for developers to carry out secondary development or maintenance, especially those who have just joined the team, and the application may be difficult to understand and modify.
(2) It is easy to cause waste of system resources
Although the service capacity in the project can be horizontally expanded using load balancing, which leads to
other services that do not need to be expanded, corresponding expansion is also carried out. This
method will greatly waste resources.
(3) Impact on development efficiency The
larger the application, the longer the startup time. In the process of development and debugging, if a large
part of the time must be spent waiting, it will inevitably have a great impact on the development efficiency.
(4) Low application reliability The reliability of the
traditional monolithic application architecture at runtime is relatively low. When all modules are running in a process
, if a bug occurs in any module, it may cause the entire process to crash, thereby shadow
affect the entire application.
(5) Not conducive to technology update
Once the traditional monolithic application architecture chooses to use certain technologies, later development and expansion will be
implemented on the basis of these technologies . If you need to change a certain technology, you may need to re-develop the entire application, this cost is very large.
