We all know that high concurrency represents large traffic . The charm of high concurrency system design lies in our ability to design clever solutions with our own ingenuity to resist the impact of huge traffic and bring users a better experience. These solutions seem to be able to manipulate the flow, making the flow more smoothly processed by the services and components in the system.
When dealing with high concurrency and large traffic, we will also adopt a similar " fighting flood " solution. We also follow the same idea in the design of the high concurrency system of Taobao APP. There are three methods in total.
- Scale-out
- Cache
- Asynchronous call
Now that we understand these three methods, does it mean that all these methods should be used when developing a system in the design of a highly concurrent system? Of course not, the design of the system is constantly evolving.
Rome was not built in a day, and so was the design of the system. Systems of different magnitudes have different pain points, and therefore different architecture design focuses. If all systems are designed according to millions or tens of millions of concurrent, e-commerce will follow Taobao, and IM will all learn WeChat and QQ, then the fate of these systems must be perished. So how do you learn?
I spent 90 days sorting out this document. I would like to combine my experience in high-concurrency projects to systematically summarize the knowledge and practical ideas that high-concurrency needs to master. I hope it will help you. This document is divided into 7 large modules. In order not to affect the reading, the catalog and part of the content are shown here in the form of screenshots, to organize and collect friends who are not easy and needy, please help me forward and reply to me by private message [High Concurrency] Get a free way to receive it !
Let us look at some of its directories below:
Basics
- Highly concurrent system: what is its general design method
- Architecture layering: why do we have to do this?
- System design goal (1): How to improve system performance?
- System design goal (2): How does the system achieve high availability?
- System design goal (3): How to make the system easy to expand?
- Interview site first phase: When asked about the principle of component implementation, is the interviewer making things difficult for you?
Database articles
- Pooling technology: How to reduce the performance loss of frequently creating database connections?
- Database optimization plan (1): How to separate master and slave when query requests increase?
- Database optimization plan (2): How to implement database and table splitting when the amount of written data increases?
- Issuer: How to ensure the global uniqueness of ID after sub-database and sub-table?
- NoSQL: How do databases and NoSQL complement each other in high concurrency scenarios?
Cache articles
- Caching: After the database becomes the bottleneck, how to speed up the query of dynamic data?
- Cache usage posture (1): How to choose a cache read and write strategy?
- The posture of the cache (2): How does the cache achieve high availability?
- Cache usage posture (3): What should I do if the cache penetrates?
- CDN: How to accelerate static resources?
Message Queue
- Message queue: How to handle tens of thousands of order requests per second during the spike?
- Message delivery: how to ensure that the message is only consumed once?
- Message queue: How to reduce the delay of messages in the message queue system?
- Interview site second phase: When asked about the project experience, what exactly does the interviewer want to know?
Distributed Service
- System architecture: Will the system with 10,000 requests per second be service-oriented?
- Microservice architecture: After microservices, how to transform the system architecture?
- RPC framework: How to implement millisecond-level service calls under 100,000 QPS?
- Registry: How to address the distributed system?
- Distributed Trace: How to troubleshoot slow requests across dozens of distributed components?
- Load balancing: how to improve the horizontal scalability of the system?
- How to do API gateway: the door of the system?
- Multi-room deployment: how to do cross-regional distributed systems?
- Service Mesh: How to shield the service governance details of the service system?
Maintenance
- Add eyes to the system: how to do server-side monitoring?
- Application performance management: how should the user experience be monitored?
- Stress testing: how to design a full-link stress testing platform?
- Configuration management: How to manage thousands of configuration items?
- Downgrade fusing: how to shield the impact of non-core system failures?
- Flow control: How do we manipulate the flow in a highly concurrent system?
- Interview site third phase: how do you prepare for a technical interview?
Actual combat
- Counting system design (1): How to do counters facing massive data?
- Counting system design (2): How to design an unread system under 500,000 QPS?
- Information flow design (1): How to do the push mode of the general information flow system?
- Information flow design (2): How to do the pull mode of the general information flow system?
Of course, the space is limited, only part of the catalog and content are displayed. If you need more content, please post it by private message [High Concurrency] to get a free way to receive it.
That's it for today's sharing. If you find it useful, I hope you can forward it a lot, and then send a private message to "High Concurrency" to get a free way to receive it. Thank you everyone~
