Yibao Payment Architect, Mobile Product Line Technical Lead, Cheng Chao, is on the road of Java

Cheng Chao is currently working in Yibao Payment as an architect. It is often said that the quality of an architect's work determines the success or failure of an entire software development project. It can be seen that the importance of architects lies in the importance of architects. In Cheng Chao's view, to be a good architect should "teach by words and deeds". As the top level of technical work, architects should be able to teach by example more than "words", and those who cannot write good code Architects cannot mentor other engineers technically.
Interview text
CSDN: Please briefly introduce you and your current work.
Cheng Chao: I am currently responsible for the management and architecture of the mobile platform product line at Yibao Payments. The projects in charge mainly include fast payment, authentication center, online banking payment and other related projects. At present, I have been engaged in Java development and management for more than 10 years. Although I have been working for a while, I feel that today's technology is changing with each passing day, and it is necessary to continue to accumulate and learn.
CSDN: How did you end up on the road as an architect?
Cheng Chao: In fact, I have been engaged in development work for the first six years of my work, and I have been continuously precipitation in technology and business. I also published some articles in some technical public accounts and blogs to summarize and share, because I I like technology very much and feel that I am more suitable for the technical route, so in the later work, my focus began to shift to the architecture. I first transferred to the company to do architecture work, and after a period of accumulation, I officially became an architect. The position began to work and has been doing architectural work for about four years.
CSDN: What role do architects play in Yibao payment?
Cheng Chao: Yibao Payment is a business-driven company. The architects are mainly divided into business architects and technical architects. In fact, technical architects are relatively common. For example, they develop some middleware in the company's platform department and carry out the secondary development of some open source projects. and packaging, etc. The business architect starts from the two aspects of technology and business, but the business is stronger. First of all, it is necessary to be able to correctly and clearly divide the relationship, boundary and responsibilities of each system from the perspective of the product, that is, to draw a business architecture diagram. Then carry out technical planning from these divided business systems, draw a technical architecture diagram, and give indicators such as scalability, performance, and fault tolerance of the overall system.
CSDN: The quality of an architect's work determines the success or failure of the entire software development project. You can see the importance of architects and how you view the work of architects.
Cheng Chao: I would like to illustrate how I view this architecture and this work through the following five points. First, as an architect, you must be able to calm down and understand the business in depth, especially in the business department. If you don’t understand the business, the architecture you design will have a feeling of illusory, unrealistic, and cannot really help the department grow. Second, I think that as an excellent engineer, we must teach by words and deeds. As the architect at the top of technical work, “teaching by example” should be greater than “words and words”, and architects who cannot write good code cannot provide technical guidance. other engineers. Third, as an architect, you must be forward-looking in technology and have insight into the latest technology direction. Fourth, it is necessary to have certain communication skills. Although architects are weaker in management responsibilities, there will be cross-departmental collaboration, and there will also be departmental technical personnel sharing training. Fifth, the architecture itself is not the goal, the simple and practical system that supports flexible expansion is the goal we pursue. What is more important in the architect's thinking is practicality and economy rather than idealization. Due to the difference between business domains and problem domains, there is no architecture that can be completely copied. In architectural design, a certain degree of scalability should be pursued, and excessive architecture and The problem of architectural idealization. As far as how to build a building, if we don't end up with a functional building, it's futile how much you brag to your clients about how reasonable your design drawings and construction framework are.
CSDN: Can you talk about the structure of Yibao payment?
Cheng Chao: Mr. Chen Bin, CTO of our company, translated and published a technical book "Architecture is the Future". This book is very detailed and rich in content, and comprehensively introduces the related work and development of architecture. At present, the technical structure of our company is becoming more and more mature and stable under his leadership.
CSDN: How has the Yipay payment platform changed since you joined Yibao Payment?
Cheng Chao: When I first joined Yibao, the original payment platform structure was outdated and could not support the rapid development of the company's business. Every time we did an event, everyone was very nervous. The performance, scalability and stability of the system It is difficult to achieve satisfactory indicators. Later, I took the lead in comprehensively sorting out the payment platform, redesigned the technical architecture of the system, and led the team to reconstruct the system. The performance, stability and scalability of the new system are better than before. A big improvement. In addition, a lot of guaranteed peripheral systems have been made for the core system, such as order process tracking system, JVM monitoring system, current limiting system, etc.
The previous system mainly realized the splitting of different systems and services through Hessian components, but Hessian required a series of other hardware devices or components to support load, routing, monitoring, etc., and the maintenance cost was relatively high, so the company's platform department was introduced. According to the components packaged by Dubbo, the original Hessian is used as a downgrade solution, which greatly enhances the stability of the system.
CSDN: It is understood that you have 10 years of Java development experience, can you share your experience in this regard? How does it apply to the structure of Yibao payment?
Cheng Chao: My 10-year work is mainly divided into two stages. In the first four years, I worked in the traditional industry, and in the last six years, I moved to the Internet industry. In fact, there are some differences between the Internet industry and the traditional industry. My personal I understand that it is a project-based company in a traditional industry, and I feel that technology is not particularly important, focusing on sales, and the number of users is not particularly large, but for Internet companies, technology can be said to dominate, such as Alibaba, If the website of JD.com and other companies crashes at a critical moment, it means that there will be a lot of economic losses, and in serious cases, it may cause the loss of users.
As far as I am concerned, 10 years of development experience is not long. During these years, I have gone through some detours and pits, and even went back to the starting point after detours and started again. I regard these as a kind of life. Cultivation requires continuous accumulation and accumulation. I have worked in the payment industry for about four years. Of course, I have experienced different companies in the process. For architects, it is necessary to increase the depth of the industry. Change in an industry, so as to become a technical expert in this industry or field.
CSDN: In terms of architecture, how did you grow and learn?
Cheng Chao: First, I mainly have face-to-face communication with the technical experts of our company and other companies, and have extensive and in-depth discussions on a certain aspect of technical issues each time.
Second, in the company, I will often break the casserole and ask to the end. Every time I will ask why it is designed in this way, what are the purposes, advantages and disadvantages of the project architecture, and whether the current architecture design meets our needs, etc.
Third, every day when I come home from get off work, I will take the technical books and study for about two hours, and record the places I don’t understand to discuss with the big cows in the industry.
Fourth, the theory with architecture is absolutely impossible without practice. At work, I will consciously think about the rationality of the existing architecture and how my code can play the best role in the existing architecture.
CSDN: What qualities do you think a good architect should have?
Cheng Chao: First, have certain communication and coordination skills. Second, it has the ability to handle sudden failures. Third, have the ability to constantly reflect. Fourth, there must be a certain technology foresight. Fifth, have excellent coding ability.