How to do a good job in high concurrency system design? I have summarized three points

hello, Hello everyone , I'm Zhang Zhang ,「 The road to the advanced architecture 」 The public name author .

Are you often asked a question in the interview ：“ If your system traffic increases N How do you redesign your system ？”

This highly concurrent problem can be solved at all levels , It mainly includes the following points .

1、 The code level

• Lock the optimization （ Adopt lockless data structure ）, Mainly concurrent Below the package is about AQS Some contents of the lock
• Database cache design （ Reduce the pressure of database concurrent contention ）, There will be another cache 、DB Data inconsistency , In practical use , High concurrency systems and data consistency systems adopt the opposite strategy .
• Merge update is adopted for data update , You can update and merge in the application layer , The same Container There will only be one at a time DB Update request .
• Others are based on BloomFilter Space for time 、 Reduce processing time through asynchronization 、 Concurrent execution through multithreading and so on .

2、 Database level

• Different storage models are selected according to different storage demands , From the early RDBMS, Until then NoSql（KV Storage 、 Document database 、 Full text indexing engine, etc ）, To the latest NewSql（TiDB、Google spanner/F1 DB） wait . Table data structure design , Field type selection and difference .
• Index design , We need to pay attention to the principle of cluster index and the elimination of overlay index sorting , As for the leftmost matching principle, it is common sense of rotten Street , Advanced indexing eliminates some sorting mechanisms, and so on ,B+ Trees and B The difference between trees .
• The last conventional means ： Sub database and sub table 、 Read / write separation 、 Data fragmentation 、 Hot data splitting and so on , High concurrency tends to divide data into buckets , There's a lot more in it , For example, how to initialize a bucket 、 Routing rules 、 How to merge the data in the final stage , The classic way is to divide the bucket into a main bucket +N A bucket .

3、 Architecture design level

• The distributed system is service-oriented
• Stateless supports horizontal elastic expansion and contraction
• Business logic level failfast Fast failure
• Call link hotspot data
• Multi level cache design
• Advance capacity planning, etc

summary

High concurrency , It often means a lot of traffic , Need to use technical means to resist the impact of traffic , These methods are like operating traffic , It can make the flow more smoothly handled by the system , Give users a better experience .

High concurrency is really a complex and systematic problem , Due to limited space , Such as distributed Trace、 Full link piezometry 、 Flexible transactions are all technical points to be considered . in addition , If the business scenario is different , There are also differences in high concurrency landing schemes , But the overall design idea is basically similar to the scheme that can be used for reference .

High concurrency design should also adhere to the architecture design 3 Principles ： Simple 、 Appropriate and rigorous . It can't be divorced from the actual situation of the business , And don't over design , The right solution is the perfect .

  welfare ： Pay attention to the official account reply key ： restructure , Free access to 《 restructure ： Improve the design of existing code 》

·················· END ··················

Official account , Free learning materials

Ten years of R & D , Big factory architect ,CSDN Blogger

Focus on architecture technology learning and sharing , Career and cognitive upgrading

Insist on sharing the dry goods of the earth , Looking forward to growing with you

---

「 The road to the advanced architecture 」 Focus on Architecture Research , Technology sharing

I'm looking at one less bug

This article is from WeChat official account. - The road to the advanced architecture （jiagou_jingjin）.
If there is any infringement , Please contact the [email protected] Delete .
Participation of this paper “OSC Source creation plan ”, You are welcome to join us , share .