Evolution of large website architectures (2) Separation of databases and application servers and Architecture Evolution

Evolution of large website architectures (2) Separation of databases and application servers and Architecture Evolution

As the number of users and concurrency increases, a single server has a performance problem. In this case, the application and database must be separated. After the separation, the entire website becomes three servers: application Server (or web Server), database server, and file server. These three servers have different Configuration Requirements for servers. application servers need to process a large number of business logic, so they need faster and more powerful CPUs. database servers need fast Disk Retrieval and data caching, therefore, a faster hard disk (usually SSD) and larger memory are required. The file server needs to store a large number of files uploaded by users, so a larger hard disk is required.

Architecture of database and Application Server Separation

 

After the database and Application Server are separated, the website performance is significantly improved, including the concurrent processing capability. We only need to work with this architecture to change the database connection address in the original application from local to another server.