background

A lot of people have asked me, “How is your microservices architecture evolving?” “, “How does the architecture of information flow go from zero to one?” “, “What is the middle platform architecture of e-commerce from 0 to 1?” “, “Can you share the full architecture? What are they like?” “, “What problems have you encountered? And how was it solved?” “, “How does the technology selection work? How is the business and the urgent integration and progress?” “, “How is the programmatic advertising related system (programmatic advertising column) built from 0 to 1? Such as DSP, RTB, SSP, etc. “, “How do I learn quickly? What are the learning methods?” And a series of questions. When I helped thousands of friends to answer or solve and discuss these problems, I also reorganized and consolidated these knowledge. Thank you for your trust and support. I will write a series of contents about this knowledge in the future (I am writing the outline at the beginning). I hope I can continue to communicate, discuss and learn with you in the future.

“Learn together, Grow together”

This slogan (the slogan of my Q group and wechat learning group), “Learn together, grow together”, has been my purpose and original intention since THE beginning of my online sharing, or rather, is my group building principles and standards. When I had the first few years of IT career, also joined the various IT group, but in the end of almost all turned into advertising group and dead group (also has some high quality group), and, of course, to maintain these groups, do need much time and energy, is understandably (so a lot of great god now planet with knowledge, mostly paid), after all free, also can’t ask others too much, Neither is the other party.

Once I pass by a lot of detours, have had a lot of tuition, so hope to be able to build a real combat dry group (qq group no. : 751925591), while to share their experience, can also help some friend go less detours, that will be a happy thing, I also can renew and thinking reflect on their own knowledge structure, etc. I have always believed that “growth is the most important thing”, and once you are truly grown, competent and experienced, believe that everything else (prospects, money, industry reputation, etc.) will follow and you will get what you deserve. Under the current state of the IT industry as a whole (society) under pressure, is my deep feeling in the last few years, “says for one thing, too many people, but so few people can really sink to do things”, so I still hope to keep doing things in a line, can do a ground gas, regardless of the future is to do technical or management.

I have been determined to be a lifelong learner (reading summary in the first half of 2018), so I hope I can keep learning and always keep the mentality of going to zero, so that I can become more professional and go further together with others. Like a word: “choose the life you want, don’t set limits on yourself”, with you.

Evolution of architecture

Good architecture is not designed, it is evolved

In this article, I hope you will find it useful to share some of the architectural evolution processes that I have led from 0 to 1 over the years

Architecture – 2017.7 –

Microservices architecture 1.0 – SpringBoot1.5

Architecture – 2018.4 –

Microservices Architecture 2.0-SpringBoot2- Dubbo-ZK

Architecture – 2018.11 –

Microservices architecture 3.0-SpringCloud

Architecture – 2019.7 –

Micro Services Architecture 4.0- Overall China Architecture (E-commerce Architecture China)

Architecture – 2020.8 –

Micro Services Architecture 5.0- Overall China Architecture (E-commerce Architecture China)

More content, updated continuously (latest update 202106)….

conclusion

In each iteration architecture evolution, related technology research or architecture design and so on, it will contain only let yourself up to a half step or step in advance (appropriate) is the most important, did not dare to go too far, because of the small and medium-sized companies, or business oriented, more like, after all, small and medium-sized start-up, the most important thing is to stick to it, can live (can earn money, Cash flow). Therefore, when making technical architecture, we also need to pay attention to the product (gameplay, cash, new, retention), design, operation and other related things. As the saying goes, “Not wanting to do technical operation is not a good product manager”.

Recommended reading

  • Architectural Thinking Growth Series (1) – The approach and practice of middle Platform architecture
  • What are we talking about when we talk about high concurrency? How do you really master high concurrency design capabilities?
  • Server – High concurrency and high availability design principles/distributed architecture evolution process
  • Summary: My twelve architectural design principles

additional

Architecture Diagram Download

  • Microservices architecture 1.0-SpringBoot1.5
  • Microservices Architecture 2.0-SpringBoot2- Dubbo-ZK
  • Microservices architecture 3.0-SpringCloud
  • Micro Services Architecture 4.0- E-commerce Platform Architecture (similar to 5.0)

My column

  • SpringBoot series
  • Framework thinking growth series
  • Microservices architecture practice
  • Practical column of programmatic advertising
  • High availability and high concurrency column
  • DevOps in Action

My CSDN home page

About me (Personal domain name, more information about me)

Github, my open source project collection

I look forward to learning and growing together with you. Thank you

Welcome to exchange questions, you can add personal QQ 469580884,

Or, add my group number 751925591 to discuss communication issues

Do not speak empty, only doer

Talk is cheap, show me the code