Introducing the Spring Cloud microservices architecture

Spring Cloud, as a framework for microservices governance, takes into account almost every aspect of microservices governance and has previously written about spring cloud articles that focus on the use of components, and this share answers both of these questions: Spring What does cloud do in the microservices architecture? How does Spring cloud offer these features to facilitate the architecture of microservices?

History of traditional architectures

Monolithic Architecture

Monolithic architecture in small micro-enterprise is more common, the typical representative is an application, a database, a Web container can run up, such as our development of open source software cloud collection, is the standard monolithic architecture.

In both cases, the monomer architecture may be selected: First, in the early stage of enterprise development, in order to ensure the rapid launch, the adoption of such a scheme is more simple and flexible, the second is the traditional enterprise with high verticality, less access pressure business. In this mode, the technical requirements are low, convenient for all levels of developers to take over, but also to meet customer needs.

Here is the architecture diagram for the monolithic architecture:

In the monomer architecture, technology selection is very flexible, priority to meet the requirements of fast on-line, but also facilitate the rapid follow-up market.

Vertical Architecture

After a period of development of the monomer structure, the company's business model has been recognized, trading volume is also slowly big up, at this time some enterprises in order to deal with the larger flow, will be the original business to split, such as: Back-end systems, front systems, trading systems.

At this stage, the system is often divided into different levels, each of which has corresponding responsibilities, the UI layer is responsible for interacting with the user, the business logic layer is responsible for the specific business functions, the database layer is responsible for the data exchange and storage at the upper level.

Here is the schema diagram for the vertical schema:

At this stage ssh (struts+spring+hibernate) is the key technology of the project, struts is responsible for the Web layer logic control, spring is responsible for the business layer Management bean, Hibernate is responsible for the database operation encapsulation, persisted data.

Service-Structured architecture

If the company is further bigger, the vertical subsystem will become more and more, and the call relationship between the system and the system is increasing exponentially. In this context, many companies consider the SOA of services. SOA represents a service-oriented architecture that divides applications into different modules based on different responsibilities, with different modules interacting directly with specific protocols and interfaces. This allows the entire system to be divided into a number of individual component Services to complete the request, and when the traffic is too large to support by horizontally scaling the corresponding components, all the components interact to meet the overall business requirements.

The advantage of SOA service is that it can be distributed, combined, and used across the network for loosely coupled coarse-grained application components based on demand. The service layer is the foundation of SOA and can be called directly by application, thus effectively controlling the human dependence of the software agent interaction in the system.

The service architecture is a loosely coupled architecture in which service splitting is the principle of high cohesion within the service and low coupling between services.

Here is the service architecture diagram:

At this stage, you can use WebService or Dubbo to service governance. Source Source

Introducing the Spring Cloud microservices architecture