Generally speaking, the top of the tech team pyramid is usually the most skilled architect (or TL). So architects probably make up less than 20 percent of the code farmers on average. Architects can also be classified as elementary, intermediate, and senior, and there are even fewer truly high-level architects in the world.
So, 80% of programmers who have been working hard for years, but still can’t be an architect, do you have the following feelings?
① My job is to complete the tasks assigned to me by the leader on time. As for how the code is written, I know there is room for improvement, but I have no time to improve. The key is that the leader does not give me time.
There are so many things I want to learn. Swoft is used by so many people. I heard that Swoole is popular recently.
③ ALTHOUGH I have been working for 5 years, I have become more proficient in Ctrl+ C and Ctrl+V in addition to Coding and writing business codes, but my Coding level has not improved. I am still an ordinary programmer, but some people have become an architect.
(4) I have been working for several years, and I want to change my job to a higher salary. The interviewer asked me about data structure, garbage collection, concurrent architecture, coroutine programming and so on. I have read it, but I don’t use it.
If you have the above questions, then you absolutely entered the learning error zone to take a detour; If we want to become architects, we face three major problems ourselves:
Identify: Who and where AM I? How to be a Good Architect: What do I do? How to build an Architect’s Body of Knowledge: What do I do?
If you want to become an architect, you might want to take a look at the roadmap I’ve shared for PHP developers 1-5 years or younger, which includes PHP high concurrency, distributed, Swoole coroutine, microservices, framework kernels, high performance, and more. These are also commonly used technologies by medium and large Internet enterprises at present, so let’s take a look in detail.
A: common patterns and frameworks
Learn PHP technical architecture, design patterns, and popular frameworks
Common design patterns, coding essential Laravel, ThinkPHP development essential latest framework YII, Symfony4.1 core source code analysis
Two: micro-service architecture and performance optimization
As the business system becomes more and more complex, coroutine programming, PHP concurrent programming and MySQL low-level optimization are the only way to upgrade the architecture. What are the technologies related to PHP performance optimization and microservices?
Tars distributed RPC framework Swoft Microservice framework server performance optimization algorithm and data structure
Three: engineering and distributed architecture
Any PPT architect who deviates from the details is a rogue, who can operate from the top and solve front-line development problems from the bottom. PHP architects need in-depth engineering, high concurrency, high availability, and massive data. It is definitely impossible to play without distributed architecture knowledge:
Linux operation /shell scripting Docker container/automatic deployment distributed cache/message middleware Distributed architecture principle/high concurrency split
Pay attention and don’t get lost
All right, everybody, that’s all for this article. All the people here are talented. As mentioned before, there are many technical points in PHP, because there are too many, it is really difficult to write, you will not read too much after writing, so I have compiled it into PDF and document, if you need to click hereShimo. Im/docs/Jky8td…>>> How to grow as an architect