Scaling equipment on the site

So, I was listening to the last Stackoverflow podcast ( episode 19 ), and Jeff and Joel talked a bit about scaling server hardware as the website grew. From what Joel said, the first few steps are pretty standardized:

  • One server running both the web server and the database (current installation of Stackoverflow)
  • One web server and one database server
  • Two load balanced web servers and one database server

They spoke little about what will happen next. Do you add more web servers? Another database server? Replication of this cluster with three machines in another data center for backup? Where does the web start from the hardware department begin?

+3
source share
6 answers

A smart setup that supports an “average” web application can evolve as follows:

  • Single combined application / database server
  • Separate database on another computer
  • The second application server with a circular DNS server (balancing with low load) or, for example, Perlbal
  • Secondly, the replicated database server (for reading downloads, requires some changes in the application logic, therefore, suitable database reads go to the subordinate)

. , , , , . Squid, , , , , .

, , , , ; , , memcached, .

, , , , , , , , , "". , , , .

, , , ; , , . , , , , ; , , , . , , .

, , , , - - ; , - , .

+10

, . , .

+2

- (-) ( Oracle RAC ..).

+1

.Net, - (, ).

0

Source: https://habr.com/ru/post/1696609/


All Articles