A brief introduction to microservice architecture

In the past two years, the microservice architecture has become more and more popular, and the projects I participate in also adopt the microservice architecture, but I usually focus on the microservice itself, and I also need to know more about the entire technical architecture.

The goal of building a PaaS cloud platform based on microservice architecture and Docker container technology is to provide our developers with a set of processes for rapid service development, deployment, operation and maintenance management, and continuous development and continuous integration.The platform provides infrastructure, middleware, data services, cloud servers and other resources. Developers only need to develop business code and submit it to the platform code base, make some necessary configurations, and the system will automatically build and deploy,
to achieve agile applications.Develop and iterate quickly.In terms of system architecture, the PaaS cloud platform is mainly divided into three parts: microservice architecture, Docker container technology, and DveOps.

Microservices focus on the size of the service, which is a component that specifically solves a problem and can be deployed and executed independently.Microservices architecture is an architectural pattern that develops a single application as a set of small services.Each service runs in its own process, and the inter-service communication uses a lightweight communication mechanism (usually HTTP resource API).These services are built around business capabilities and can be deployed independently through a fully automated deployment mechanism.These services share a minimal centralized management.

In a nutshell, the microservices architectural style [is an approach to developing a single application as a set of small services, each running in its own process and via a lightweight mechanism (usually HTTPresource API) to communicate.These services are built around business functionality and can be deployed independently by fully automated deployment mechanisms.There is little central management of these services, it can be written in different programming languages ​​and use different data storage technologies.

Microservices are a group of services with a single responsibility instead of a single application; each service runs in its own process and adopts a lightweight communication mechanism with each other, such as RestFul, etc.; services are autonomous and can be independentCompile, deploy, and go online; decentralization, the smaller the management overhead, the better; the technologies adopted by services are diverse, and different services can adopt different technology stacks.

The microservice structure has the following disadvantages: technically it is a more complex distributed architecture, the way of data partitioning also brings a lot of difficulties to data consistency, and the relationship between services is also more complicated.However, since the microservice structure has the ability to handle complex things and requirements, can quickly respond to changes in demand scale and characteristics, and can handle revolutionary market changes brought about by new technology innovations, we still choose a PaaS automation-based microservicemain structure.

PaaS is the abbreviation of Platform-as-a-Service, which means platform as a service. On this platform, it provides application hosting and service management, operation support optimization, development process support and service capability opening.That is, this platform provides support and management for the entire process of birth, compilation, launch, opening, scaling, termination, and offline of a network application.

A comprehensive article on microservices:
Reference Article – Microservices
This article explains the microservice architecture in detail