Preface
Do you know what abilities are required to become an architect? In fact, the level of personal ability depends on many factors, and they satisfy the following relationship:
Ability=f (cognition, insight, practice, experience summary)
I don't know which stage you are at?
Architecture is the practical art of software engineering. It is necessary to turn ideals into reality, not castles in the air. No matter how much design philosophy and methodology you know, you can say it is not practice or fake it. Only when it is done and recognized is the real skill. This article brings together many successful cases in the industry, without empty talk, full of sincerity!
The "service", "architecture", "model" and "design" in the field of software research and development are all concepts derived from the metaphor of work in other fields such as architecture. Therefore, for many practitioners, what they mean specifically can only be understood and cannot be explained in words.
This article tries to sort out the methodology, then cut into the microservice architecture, conduct in-depth deduction, and finally supplement a large number of actual business scenarios to allow readers to better understand and digest the meaning and construction methods of "architecture". It is an abstract theory and practical experience. A combination of masterpieces.
This article gathers the wisdom and wisdom of many senior architects in China, and explains in detail the four aspects of architecture methodology, microservice architecture, business architecture, and performance optimization. To learn architecture knowledge, you need to refer to such a good article. Friends who want to learn architecture knowledge in depth are recommended to read this book.
I hope this article can help you build up this kind of architectural thinking, continuously improve your own technical depth and breadth, and make yourself more valuable. I hope this article can help you learn, and forward it a lot to benefit more people. ! ! !
table of Contents
main content
This article will be divided into four parts to give you an in-depth introduction to what abilities and skills you need to become an architect:
Chapter 1 Architecture Methodology;
1. Conceptual cognition about architecture; architecture is a highly comprehensive professional field. The role of software architecture is essentially the same as that of the basic architecture of a building°. To become a qualified architect, you must not only have knowledge in the field of computer science or software engineering, but also in-depth study of philosophy, mathematics, and some common sense of architecture, and broaden your horizons. Under normal circumstances, you need to experience programmers. , Software designer and other stages, and finally become a software architect.
The architecture is not mysterious or superior. It is in practice. As long as you study carefully and think actively, there is a lot to do in the field of architecture.
2 Architectural design starting from the end; in summary, the work of software architecture may seem simple, but it is not. Systematic thinking helps to clarify the software architecture process and from the perspective of customer value. Identifying users and setting SLAs can help software architecture designers and R&D personnel avoid getting lost in the complicated technical journey and falling into "self-heavy". The architecture has evolved. The architecture contains a series of decisions and several components. When designing the architecture, you should look at the problem from a global perspective.
3 Closed-loop architecture methods; this chapter summarizes some feedback loops that software R&D organizations often need to pay attention to in terms of products, organizations, processes, and architecture, as well as the supporting technologies and architectural methods needed to strengthen these feedback loops. The improvement and promotion of software R&D organizations in these areas has certain guiding value. In addition, I hope that the content shared in this chapter will have certain guiding significance for R&D engineers and architects to establish closed-loop feedback and DevOps awareness.
The content of this chapter is mainly based on the summary and thinking of the previous work. The purpose is twofold. On the one hand, it is to sort out one's own ideas and make some precipitation, and on the other hand, it is to stimulate everyone's further thinking. If there is any improper understanding or bias, please feel free to advise.
The content of this chapter is mainly aimed at software research and development organizations that provide SaaS services, and other types of organizations involving IT systems can also learn from it.
4 The relationship between complexity and architecture evolution; a long way to go, dealing with the complexity of software systems is an eternal topic. Although there are endless methods to deal with complexity (including tools and R&D processes), the complexity of software systems will also evolve with technological development. The relationship between the two is the Tao and the magic in the software system. Although "the Tao is one foot high, the magic is one foot high", we still need to do everything we can to defend the software. There are no shortcuts. The only thing that can be done is to actively seek solutions after understanding the reasons for the complexity of the software, such as diagnosing the disease, identifying the cause of the disease, and then prescribing the right medicine.
5 The core competence of an architect; in many years of architecture work, I often ask myself what I should do and how to do the architecture work well. This chapter intends to summarize my own experience and views on architecture work in terms of responsibilities, core capabilities, and ability training. To be an architect, one must look up at the starry sky and crawl forward. Looking up is the vision and direction, and creeping is to have control over the business and specific research and development, and avoid becoming a "PPT architect" in the sky.
Chapter 2 Architecture-oriented architecture (microservices); Microservice architecture is an architectural pattern and an interesting way of thinking. Its main function is to decompose functions into discrete services, thereby reducing the coupling of the system , And provide more flexible service support. Each service in the microservice architecture runs in its own independent process, and a lightweight communication mechanism is used between services to communicate with each other. Each service is built around a specific business and can be independently deployed to the production environment , Production-like environment, etc. This article will introduce the details of microservices and the advantages and disadvantages of microservices from the concept to implementation of microservices.
6 Quickly inherit the practice of microservices; in general, microservices have their own advantages, as well as problems that need to be faced. The complexity brought by distributed systems cannot be ignored in the microservice architecture model, and the further distributed collaboration brought about by service segmentation poses more challenges to engineering practice. In addition to basic service-oriented capabilities, microservices must also carefully deal with issues such as inherent performance, partition fault tolerance, consistency, and security of distributed systems. At the same time, microservices put forward higher requirements for the ready functions of the production environment, covering the complete life cycle from development, testing, release, operation and maintenance, monitoring, offline, etc., especially in improving development efficiency, service governance, monitoring, and Cloud Native architecture models , Resource virtualization and automation level need to do more work to better implement microservices.
7 Transaction processing under the microservice architecture; this chapter mainly introduces the CAP theory of distributed systems, and at the same time summarizes and compares the advantages and disadvantages of several distributed decomposition schemes. Distributed transaction itself is a technical problem. There is no perfect solution to deal with all scenarios, and the decision must be made according to specific business scenarios.
8 Microservice architecture patterns and practices; in general, the core principle of Rainbond in Service Mesh microservice architecture is openness, and provides users with out-of-the-box, powerful and simple access through standardized access of various excellent solutions Microservice experience.
9 Microservices and DevOps architecture practice; DevOps organizes the team according to the business, and the team includes design, development, testing, operation and maintenance personnel, so that on the one hand, it can effectively reduce the internal consumption caused by the internal modification of the service; on the other hand, the team boundary Can become clearer.
DevOps is actually a cultural change that breaks the barriers between traditional development and operation and maintenance, and helps organizations form a fully functional and efficient team from development, testing to deployment, and operation and maintenance.
10 Cloud-based microservice architecture; under the microservice architecture, services can be fully decomposed according to functions and responsibilities, and dependencies can be decoupled. A single service is easy to develop and maintain, which can achieve a shorter development iteration cycle and promote agile development and continuous deployment. However, we must also fully realize that microservices have the complexity brought about by the inherent characteristics of distributed architecture. The communication between a large number of services puts forward higher requirements on the integration testing, stability, operation and maintenance and monitoring of applications. CAР theory Constraints also bring greater challenges to data consistency. Microservice architecture requires high investment in infrastructure. Simple applications adopt a single architecture to be more economical and effective. Only when large and complex applications adopt microservice architecture can the value of investment be reflected.
11 Service Fabric platform architecture analysis: As a system hosting platform developed and used by Microsoft for more than 10 years, Service Fabric has distinctive features, complete functions and powerful features.
Not only provides a unique programming model to make it easy to develop applications oriented to the microservice architecture, but also allows legacy systems to enjoy the powerful capabilities of Service Fabric through the guest or container model.
The third chapter business-oriented architecture;
12 how to build a highly scalable mobile e-commerce architecture. This chapter introduces the scalable mobile e-commerce architecture, including mobile hybrid architecture, server-side SOA architecture, container-based virtualization, and how to apply elastic cloud and other technologies to deal with large-scale e-commerce promotion scenarios with high traffic and high concurrency. Inspire you to build a highly scalable mobile e-commerce architecture.
13 How does the consumer credit system "Baifumei" continue to be optimized; the technical architecture of "Baifumei" has expanded from a simple single application to a micro-service architecture. The division of labor is becoming more and more detailed, and the requirements for professionalism are also increasing High, this requires us to precipitate core service capabilities to quickly support the development of the business, and to ensure the stable support of the system, which brings us very big challenges.
Up to now, "Baifumei" has provided convenient services to millions of users, generated tens of millions of bills, and has experienced many group promotion activities. More and more users are serving. We are burdened by this. It is getting heavier and heavier, and the things to be done later are getting harder.
14 The evolution of the payment system architecture of Meili Group. Through business sorting, system boundary splitting, business modeling and other processing, we have completed the architecture upgrade of the payment system 2.0, which can provide more efficient, stable and professional support for the business , And improve the accounting and management capabilities of funds.
In the future development, the upper-level payment acquiring business will provide more business support based on the characteristics of e-commerce, and the lower-level fund settlement will provide accurate closed-loop accounting. At the same time, it is necessary to find all the improvements in the performance and capacity of the platform, and continue to To optimize. Funding is no small matter, and how to improve the stability of the payment system must be a key consideration.
15 Financial matching framework, through understanding the current electronic commodity trading market trading system and transaction process, familiar with the electronic commodity trading market order matching method and mechanism, and convert it into a detailed flow chart, which lays the foundation for the design of the matching system.
This chapter abstracts the needs of the matching system from the transaction mechanism, divides the system into multiple functional modules for detailed architecture and design, and at the same time, in order to build a high-performance, high-reliability and high-scalability transaction matching system, based on multi-layer distributed The system and J2EE technology are designed and implemented, and the latest memory matching technology is adopted, and the multi-level storage mode is used to improve the operating efficiency of the system. With the increasing expansion of the electronic commodity trading market and the increasing requirements of stockholders on system performance, how to construct a high-performance matching trading system requires further research in the electronic commodity trading market.
This chapter simulates the electronic commodity trading market by constructing an electronic commodity trading matching system based on a multi-layer distributed architecture, thereby fully demonstrating the operation mode of the electronic commodity trading market and providing a basis for further research.
Chapter 4 Performance-oriented architecture;
16-line architects will show you performance optimization; performance optimization, like projects, has the three characteristics of temporary, unique, and gradual, whether it is to urgently deal with production performance problems, or for To prepare for promotional activities, you must plan before performance optimization. The 5W+1H principle is more practical here:
17 Common patterns and trends of performance optimization; this chapter hopes to summarize the patterns of performance optimization so that readers can understand common performance moves, and through these moves, they can find performance bottlenecks in their own system, or clarify the current application. The development stage and the model that may evolve in the next step.
Performance is one of the main driving forces driving the evolution of the application structure. This chapter reveals how performance drives the application structure to evolve toward the next structure at different stages through changes in the application structure. The development of application structure can also reveal how to support the development of enterprise business without excessive design and application as simple as possible and without wasting enterprise resources.
18 Several common stress test models for performance optimization and their advantages and disadvantages; the several stress test models introduced in this chapter are the main models currently used, and there may be some variant models, but they will not be too different. There are also some points that need to be paid attention to during pressure testing, such as being careful about the bottleneck of the press. Now the commonly used tools include JMeter, etc., which will not be explained in detail here.
19 Cache is king-wireless cache architecture optimization; there is no perfect architecture in the world, and an architecture that can support the needs of evolution and meet the current needs is a good architecture. Just the right thing is the goal we pursue. The flexible use of wireless cache and the well-knowledge of its limitations and advantages are very beneficial to the design of the mobile terminal. In addition, this also allows architects to consider the mobile and server side as a whole, instead of considering the problem from a single perspective (designing the server side means designing the server side separately, and designing the mobile terminal means designing the mobile side separately), so that The evolution direction of the architecture is more scientific and healthy.
This [Architecture Collection] has 281 pages. Friends who need the full version can forward it to the editor and scan the code to get it! !
to sum up
The term architecture originated from the field of architecture and refers to a system composed of various components. The software architecture must be described in terms of reliability, security, scalability, and scalability.
And this article collects the strengths of many technical experts, based on theory and starting from actual combat, and brings together a lot of practical architecture schemes. It is a tool book worth looking forward to.
I hope this article can help everyone learn, and I hope it can be liked by everyone, repost a lot and pay attention to not get lost, so that everyone can learn how to become an architect! ! !