Microservice architecture design pattern-(1) Problems with monolithic architecture

Monolithic architecture

  • advantage
    • Simple
    • Testing is intuitive
    • Easy to deploy
    • Simple horizontal scaling, i.e. running multiple instances
  • question
    • complex
      • As the system becomes larger, it becomes more complex
    • Development is slow
      • If you change a small point, you need to package and run the entire project.
    • Difficult to expand
      • Some modules require simple configuration, some require advanced hardware configuration, and the entire project is a configuration
    • No fault isolation
      • If a module fails, the entire project will fail.
    • Difficulty in upgrading technology
      • When trying new technologies, you need to change all relevant places, which is very costly.

In my opinion, the increase in complexity makes it difficult for monoliths to

  • Complexity is made up of elements, and the relationships between them
  • More elements
    • Everyone disagrees
      • Some have high requirements, some have low requirements
  • There are more relationships between elements
    • If you want to make changes, I will be affected.
    • You hang up, I hang up too
    • If you want to update, I should update accordingly.
    • Programmers just want to change you, but they have to get to know your brothers and sisters too

Guess you like

Origin blog.csdn.net/u014704998/article/details/128171367