### 单体架构的优点
In the early days of FTGO, when the application was relatively small, the application’s monolithic architecture had lots of benefits:
* Simple to develop—IDEs and other developer tools are focused on building a single application.
* Easy to make radical【快速】 changes to the application—You can change the code and the database schema, build, and deploy.
* Straightforward【直接的】 to test—The developers wrote end-to-end tests that launched the application, invoked the REST API, and tested the UI with Selenium.
* Straightforward to deploy—All a developer had to do was copy the WAR file to a server that had Tomcat installed.
* Easy to scale【扩展】—FTGO ran multiple instances of the application behind a load balancer.
Over time, though, development, testing, deployment, and scaling became much more difficult. Let’s look at why.
- 空白目录
- 1. Escaping monolithic hell
- 1.1 The slow march toward monolithic hell
- 1.1.1 The architecture of the FTGO application
- 1.1.2 The benefits of the monolithic architecture
- 1.2 Why this book is relevant to you
- 1.3 What you’ll learn in this book
- 1.4 Microservice architecture to the rescue
- 1.5 Benefits and drawbacks of the microservice architecture
- 1.6 The Microservice architecture pattern language
- 1.7 Beyond microservices: Process and organization
- 2. Decomposition strategies