当前位置：网站首页>Abused "architect"!

Abused "architect"!

2022-04-23 01:23:00 【InfoQ】

In the minds of many programmers , There will be such a path to play strange and upgrade ：

null
once , I have no doubt about this path , Now think about it. , Maybe it's because the Jianghu I saw as a beginner is too small . Slowly, , I've been in the Jianghu for a long time 、 The view is open , I found myself thinking too simply .

The first 1 Yes “ Architects ” The definition of

More than 10 years ago , When I first entered the Jianghu , First, I entered a large software company located in Shenzhen , The scale of R & D personnel is thousands . The person who interviewed me is said to be an architect in the company , I was really full of admiration for this architect at that time , So far I can vaguely recall his face and voice .

The mainstream back-end technology at that time was Struts+Spring+Hibernate, That is what the industry often said at that time SSH; The mainstream technology of the front end is HTML+jQuery+ Native JS. There was no management at that time jar Packet dependent maven, There is no out of the box SpringBoot, If you want to integrate the above technologies for developers in a new project , It often takes days or even weeks , And these jobs are the responsibility of architects .
therefore , I gave the architect the first definition ：
Architects
Is to integrate various frameworks into one project , Provide common code , Support developers to complete the development of business functions and provide necessary technical support .
Then I returned to Xi'an , I am now , With their own continuous efforts , I have mastered the above technologies very well . In a small software company in Xi'an , I also became an architect , At the same time, I set a working principle for myself ：
Not involved in the development of business functions , Only provide general ability and technical support for programmers .
In the years that followed , I always stick to my definition of architecture , Principle business knowledge , Focus on all kinds of cool technologies , It has also been the last line of defense in the team to face difficulties and provide support for developers .

The first 2 Yes “ Architects ” The definition of
Now? , I've been fighting in the Jianghu 12 year , In the position of architect, there are already 8 About years ago , Originally, I simply thought “ The architect is the peak ” Of me , I lost my way for a while . After continuous communication and many interviews , It seems that in everyone's heart , Yes “ Architects ” The understanding of this noun is different .
There is a , When attending an architect training camp , I was deeply impressed by a picture in the training materials , Although I can't find the original picture , But the idea expressed is shown in the figure below ：

null
The lecturer likened an architect to a conductor in a symphony , In his description , The architect's perspective should be higher than others , The focus is not on individual specific issues , Instead, it should be considered from an overall perspective 、 The overall planning , Then instruct others to put the plan on the ground . If the architect goes too deep into the details , It will only make him lose his way because he can't look up at the road , It's like “ I don't know the truth , Only the body in this mountain ” equally .
therefore , I am right. “ Architects ” With the second definition ：
Architects
Is to look at problems from a higher perspective than others , Command the overall situation with a higher perspective , People who don't stick to technical details .
But such a definition also made me constantly challenged by the interviewer in the subsequent interview , In most interviews , The interviewer's requirement for the architect is still the depth of a certain technology , Rather than the overall breadth of Technology .

The first 3 Yes “ Architects ” The definition of
In recent years' work experience , I came into contact with another kind of architect , They are often called “ Solution architect ”、“ Industry architect ”、“ Delivery architect ” and “ Pre sales architect ” etc. .
When I first engaged in this kind of work , I revisited the two definitions given to architects before , It seems that the work content at this time is completely different from those two definitions .
After nearly 2 Years of experience in the position of solution architect , It is found that such architects actually exist as consultants to customers . The work content is almost out of coding , But to give a certain technology and product system , Before customers buy 、 in 、 Provide personal consulting services after , Help customers plan the technical direction 、 Product portfolio and providing practical solutions, etc .
here ,“ Architects ” The third definition of was born in my heart ：
Architects
Is to stand at the strategic level , Provide overall solutions for information technology in enterprises 、 Work roadmap of the supervisor, etc .
Later, I got some “ Golden certificate of architect ” Of TOGAF, Also opened to me “ The enterprise architecture ” Gate , This also makes me more convinced of my third definition of architect .

“ Architects ” That's not the definition
Although I have a view of architects in my heart 3 Definitions , However, far from making my understanding of architects clearer , It makes me more confused . Especially when interviewing for the position of architect , Obviously I'm strong , But I always feel that my conversation with the interviewer is not on the same channel . This once made me doubt my ability , Started self denial .
After deep thinking and reading relevant materials , I find ,
The root of the problem lies in “ Architects ” The abuse of this term
.
Martin Fowler（ One of the proponents of microservice Architecture ） In one of his articles on architects, he said ：
No matter what the architecture is , It contains important things , The architect is the person who pays attention to these important things .
In my submission ,“ Architects ” The abuse of this term , It is precisely because this post focuses on important things , therefore , When recruiting in the industry , As long as something important is involved , It will be called “ Architects ”.

Classification of architects
Actually , There are many kinds of architects , Each type of architect has its own growth path —— This is different from the monster upgrade .
First , I will “ People who focus on what they want ” Split into three categories , As shown in the figure below ：

null
  • Common technical experts are ：
    Database architect 、 Cache architect 、 Framework architect 、 Workflow architect ”、 Big data architects, etc , These architects focus on the technical details of the corresponding field .
  • Common products 、 Industry experts have ：
    Pre sales architect 、 Solution architect 、 Delivery architect 、 So and so industry architects , These architects are not focused on R & D and Technology , It lies in the general demands of a product system or an industry .
For the... In the picture above “ Architects ” for , You can continue to split , As shown in the figure below ：



null
  • R & D architects ：
    For one IT Project or product leader , Blame IT Technical planning of the system 、 R & D, operation and maintenance . Common job names are ： system architect 、 software architect 、 Technical architects, etc .
  • Business architects ：
    It is common in all walks of life , Responsible for planning the business logic of their enterprise . Common job names are ： Domain expert 、 Business architect 、 Chief designer, etc .
  • Enterprise architect ：
    It is common in all walks of life , Responsible for internal and external management IT Planning and construction of the system . In Africa IT In the enterprise , Mainly responsible for the internal management of the enterprise IT Construction , Provide information support for business departments ; In software or Internet, etc IT In the enterprise , You can only be responsible for the internal system of the enterprise or both internal and external systems .

How architects work

The working methods mentioned here are mainly divided into two categories ： Centralized and connected .

（1） Centralized architects
Centralized architects usually have outstanding capabilities in a certain field , In order to “ Problem Terminator ” The role of appears in the team , When problems arise that other team members cannot handle , Centralized architects will be the last line of defense of the team .
The advantages of centralization are ：
  • As the sole decision maker , Can effectively unify ideas within the team , Ensure consistency within the team .
  • As an experienced and technical expert in the team , It will bring a sense of security to other members .
The disadvantages of centralization are ：
  • As the sole decision maker, centralized architects can effectively unify their ideas , But in practice , Architects are often not the closest to the problem , Misjudgment by architects is also common , Because centralized architects are the only decision makers , Other members can only follow , Therefore, it is very likely to make the wrong decision .
  • The centralized architect's strong personal ability brings a sense of security to other members at the same time , It will make other members rely on centralized architects , Lead to the reduction of the enthusiasm and initiative of other members , The work intensity of centralized architects increases .
（2） Connected
Connected architects are like adhesives , They are better at cooperating with others . Such architects may not have outstanding personal technical capabilities , But they have rich experience and communication skills , Through deep cooperation with different functional teams , Assist the team to solve problems , Provide corresponding resources and authorization for the team when necessary . in addition , Connecting architects will be a bridge between technicians and non-technicians , Connect business and technology departments .
In the early days of my work , I am very supportive of centralization , Because I think such communication costs the least 、 Highest efficiency , But for now , Its shortcomings can not be ignored , also , The larger the system, the more obvious the disadvantages are . Therefore, my current recommendation is to focus on the connection type , Centralization is supplemented by .

summary

The author combines his own experience in software R & D industry 12 Years of work experience , Put forward the requirements for the position of architect in different stages 3 Species definition . During the discussion with various groups for architects , obtain “ Architects ” The word is widely used in the industry “ The abuse of ” This conclusion .

After deep thinking about the position of architect , The classification system proposed by the architect . The author thinks , Abused “ Architects ” The word actually means including technical experts 、 Architects and products 、 Different directions including industry experts , And continue to classify the direction of architects as ： R & D architects 、 Business architects and enterprise architects .
All in all ,
Architects focus on important things , The perspective should be higher , Avoid getting into details ; The bigger the system , The more connected architects are needed , When the team hesitates , Centralized architects need to make quick decisions .
▼
More about it , Welcome to the author's new book
《 Enterprise architecture and inseparable microservices （ Two colors ）》
！



Enterprise architecture and inseparable microservices （ Two colors ）.jpg
▊《 Enterprise architecture and inseparable microservices （ Two colors ）》
Fan Chao   Writing

  • In theory , Introduces the enterprise architecture standard 、 Cloud native ideas and related technologies 、 The past and present of micro service , And domain driven design ;
  • In practice , This paper introduces the method for splitting microservices “ Five steps ”、 contain 4 A dimension “ Enterprise Cloud original generation maturity model ”, And measuring the results of enterprise change “ Effect and benefit evaluation method ” etc. .
The core content of this book includes ：
  • The definition of enterprise architecture and the responsibilities of enterprise architects ;
  • Whether the enterprise architecture is well designed is the basis for judging ;
  • Cloud native related ideas and technologies ;
  • The origin of microservices 、 Evolution 、 characteristic 、 Split method and landing guide ;
  • Opportunities and changes brought by cloud native to enterprises .
This book can help enterprises identify pain points 、 Set principles 、 Planning the path 、 Capacity building and evaluation of effectiveness , Finally realize the continuous operation and continuous evolution of micro service architecture in the enterprise , So as to meet the increasing business challenges .

版权声明
本文为[InfoQ]所创，转载请带上原文链接，感谢
https://yzsam.com/2022/04/202204221019330862.html

边栏推荐

猜你喜欢

随机推荐