The word is like the face, I am Brother Jun!
It is said that architects not only make more money, but are also admired by programmers and admired by girls.
They walked with the wind and played with their own BGM. They blew and blew, and my pride was indulged. The only drawback is that it takes a long time to wear your hair .
Although an architect is good, not everyone can be one. In addition to being extremely smart, one must also have a solid technical foundation. After years of hard work, I have achieved something, and I am already the best .
An architect must be experienced in many battles and experience numerous major downtime incidents. Because the sharpshooters are fed by bullets, and every piece of fat on the body is eaten by you yourself. There is no other, but you are familiar with it .
As the rider who knows the most about architecture among the technical leaders, I not only deliver good takeaways , but I have also crashed many large-scale systems . Let’s talk about it based on my own experience: How to build a technical architecture that can bring down the company?
1. The main link of the system should be as single as possible
A single-point system, just like the Suez Canal, once the waterway fails, the entire transportation system is paralyzed, which is very sour.
A la carte is like being single. It feels uncomfortable at first, but don’t worry, because you will get used to it later .
2. Use multiple loops in the program
Infinite loop is one of Lao K's favorite programming techniques. When you see the CPU utilization rate is 100%, you know that you should pass the blame to operation and maintenance.
These days, it's really hard to do without some special skills. For example, I am a good instrument--I am very good at retreating .
3. Increase dependencies between systems
Add internal dependencies, external dependencies, and third-party dependencies to the system. In short, if you can rely on it, never write it yourself.
Old K's achievements today are mainly due to my strong hands-on ability. There are only two things I can't do in my life: I can't do this, and I can't do that .
4. No service compensation
Many things, if you miss them, you miss them. There is no way to make up for it. This is life.
As an architect, you must have a high level of philosophy.
So, young man, you only saw the second level, and you only thought of me as the first level. In fact, I am the fifth level . Do you know what I mean?
5. Don’t do idempotent design
Why should the backend interface be designed to be idempotent? Doesn’t the front end make any judgment when submitting? Leave it all to back-end development?
We are all workers. People need face, trees need bark, and telegraph poles need cement .
6. Do not set a timeout
The connection timeout and read timeout are set to 60 minutes regardless of internal or external calls.
As long as you work hard, there is nothing that cannot be done in time. If you can't be friends with time, be friends with time .
7. No traffic control
Let the traffic come more violently, and don't limit the traffic. The leaky bucket algorithm and the token bucket algorithm are not as good as the beer bucket algorithm - sleep after drinking, and love whoever you want .
What kind of traffic is still being controlled?If you can't even control your weight, give up now. Look at Bajie. He has traveled thousands of miles and yet he has not lost any weight. Moreover, he is also a vegetarian .
8. No monitoring and early warning
We are all working adults, do your job and don’t meddle in other people’s business.
After working for several years, I understand a truth: skillfully using "none of my business" and "none of your business" can save 80% of the time in life .
9. No retry strategy
The service call failed, do you want to try again? I am not a casual interface.
Life cannot be repeated, let alone messed up .
Do not believe? You ask the doctor to prescribe you some regret medicine and a cup of love-forgetting water, and the doctor will immediately send you to a mental hospital .
10. No system isolation
Never isolate the system, hang it all together.
What is a true brother? That is, when a brother needs a woman, step forward and be his woman .
When faced with a troubled man , you should eliminate thousands of men and welcome the man .
11. Code synchronous call
To build a system, we need to be consistent and harmonious, make calls as synchronously as possible, and write as many bugs as possible.
Usually when I write bugs, I like to write at noon. Do you know why? Because sooner or later there will be retribution .
12. No hot data caching
What is the significance of RPC? It's just called. Calling like crazy is the most basic respect for a service.
Do you know why big projects have to choose a good day to launch? Let’s put it this way, do you think there will be good times after it goes online?
13. No system classification
Systems should be treated equally, without distinguishing between core systems and non-core systems. Have you ever considered how the system feels?
Would you be happy if you were categorized? Looking back, we were all very happy when we were children, because at that time, being ugly and poor were not so obvious to us .
14. No service downgrade
If the service is downgraded, it will be low. Even if it goes down, we still have to bear it together.
There is no such thing as a wasted journey in life. If there is, then there is a bug in the WeChat movement .
15. No grayscale and rollback solutions
Going online depends on luck, there is no rollback plan! Just so confident.
As a person like me, I have mastered a special skill without learning anything else when I grow up. I can sleep peacefully without sleeping pills during the day, and I can be excited without stimulants at night .
When it comes to staying up late to publish, I have never convinced anyone.
16. Programs make more remote calls
What can be called remotely will never be called locally. In the 5G era, network delay is nothing.
Besides, you have to be patient. Your girlfriend is one hour late for a date. Do you dare to get angry?
Just don't dare, don't mess with women, they are animals that will bleed for a week and not die .
17. No fuse mechanism
Are you getting dizzy from stock trading? How about a circuit breaker?
Have you asked Queen Li Ling? How green is the fund? Did he call for a circuit breaker?
As a leek, you still have to pay tuition. Pay more when you are young, so that you will get used to it when you are old .
18. No code scanning
You must have the spirit of craftsman and review your own code. How will the machine know how to appreciate your code art?
My sultry comments, wonderful functions, and uncanny Copy/Paste. Every time I look at the code, I am amazed by my talent .
19. No online pressure testing
Once you go online, that's it. Leave the rest to Bodhisattva.
no pain no gain. There is no such thing as a free lunch, so I usually sleep until the afternoon .
Finally, I want to say that there are many more tricks in architectural design. If any of the above is taken to the extreme, it is enough to bring down the company.
Architect is the profession closest to a saint. Excellent architects think about themselves three times every day: what to eat for breakfast, what to eat for lunch, and what to eat for dinner .
Finally, may God bless every architect who has enough to eat.
Finally, let me give you a preview. This Saturday night at 21:15, I will give a topic about technical people "Breaking the 35-year-old crisis: How 25-35 technical people can make career plans". Those who are confused about the future will not be able to find a job. If everything goes well, if your career plan is not clear, or if you don’t know what core competitiveness you should have at the current stage, you are welcome to come to the live broadcast room with your questions, and we’ll see you there~
Recommended popular articles from the past:
How to manage upward? From a real case!
Breaking the 35-year-old crisis: How do technical people plan their careers? !
For more exciting news, follow my official account and learn and grow together.
