Black Friday is coming. Designing a system with extremely high concurrency, high availability and quick responsiveness needs to consider many aspects all the way from frontend to backend. See the diagram below for details: Design principles: 1. Less is more - less element on the web page, fewer data queries to the database, fewer web requests, fewer system dependencies
Instead of "nginx", would it be better to say "reverse proxy" as the general concept?
we can use multi-master cache to divide the load
For the customer experience, maybe we need to decrease inventory first before doing payment...?
What is TPS here ? I am noob.
For high concurrency, implement load balancing to distribute the traffic evenly across multiple servers and prevent crashes due to server overloading.
Having a backup system in place for high availability, so that the website can still function in case of technical issues.
Performance testing to verify the system scales to handle spike in the traffic during the Black Friday event.
Use gzip compression in front end to improve UI performance.
I dont understand how isolating the cache and db isntance helps in this case