Table of contents
Cloud-native gateway gradually takes shape, service grid returns to rationality
The layering of microservice architecture is gradually clear
Microservice technical standards gradually formed
Integration of SidecarProxy and Proxyless modes on the data plane
Service governance data plane transparency, control plane standardization
Distributed transactions from diversification to standardization
Multilingual solution standardization
Service Mesh Technology Returns to Rationality
Cloud-native gateway gradually takes shape
Cloud-native gateway gradually takes shape, service grid returns to rationality
With the advancement of open source and cloud computing, cloud-native microservices as the core technology have maintained a rapid growth rate of about 20%; with the maturity of microservice technology, the threshold has been greatly reduced, and it has begun to penetrate into all walks of life; on the one hand, labor costs continue to It is imperative to use microservices to improve R&D efficiency; on the other hand, the post-90s generation has become the main force of R&D, and the advantages of independent and agile microservices are more popular among young people.
Microservice technology is gradually maturing, the layering of microservice core architecture is becoming clearer, technology standardization and industrialization are taking shape, hot service grid technology is gradually returning to rationality, cloud-native gateways are gradually taking shape as the next-generation gateway technology, and microservice technology as a whole has entered deep water district.
The layering of microservice architecture is gradually clear
The layered micro-service architecture is gradually formed, the back-end is BaaS, the client is lightweight, and the business side is Serverless, which makes the business more focused on business development and further improves the efficiency of research and development.
Microservice technical standards gradually formed
Istio/Envoy has become the de facto technical standard for the control plane and data plane of the service grid. Microservice competition has entered the deep water area. Service grid, service governance, distributed transactions, and zero trust will become differentiated competitiveness.
Integration of SidecarProxy and Proxyless modes on the data plane
Due to factors such as sensitive RT of some links and limited upgrade environment, the Sidecar model cannot be solved well. With the development of Sidecar, the standardization of the data plane has been promoted. At present, gRPC already supports the xDS protocol, and Dubbo has initially provided the service discovery of the xDS protocol. It is expected that in March, the Dubbo community will provide comprehensive xDS service governance support and complete the integration of SidecarProxy and Proxyless models.
Service governance data plane transparency, control plane standardization
The data surface of service governance will gradually sink, gradually decoupled from business logic, and transparently realize the evolution and upgrade of governance technology. From the perspective of the form of the data surface, there are many forms coexisting. For the Java language, the service governance technology in the form of Java Agent is emerging and gradually becoming a trend. For non-Java languages, the Service Mesh technology based on Sidecar is being increasingly adopted. More and more companies adopt it.
On the control plane, using a set of control planes to control different data planes has become the mainstream, and will gradually be unified into the service governance control plane centered on Kubernetes CRD. The scope of service governance extends to the full life cycle of development, testing, release, operation and maintenance, security and other scenarios.
Distributed transactions from diversification to standardization
Data is the core asset accumulation in the digital transformation of enterprises, and the problem of data inconsistency at the application architecture layer is particularly prominent in the microservice architecture. The core value of distributed transactions is to quickly help architecture developers solve the problem of capital loss and goodwill that may be caused by data inconsistency through the framework, so that they can focus on the design and development of the business itself.
In the past, the implementation of distributed transaction schemes was complicated and diverse, and it was difficult to unify. The coupling between schemes and businesses was difficult to reuse, the consistency of complex scenarios was difficult to guarantee, and the lack of endorsement by major manufacturers and large-scale traffic verification was difficult to promote implementation. This has also led to a long-term stagnation in the development of distributed transactions.
With the open source of Ali Seata, the concepts, roles, models, and patterns of distributed transactions have been extended and abstracted to make them conform to the architecture design of microservices. Through the abstraction of the engineering framework, it further evolves into the transaction standard, so that multiple transaction solutions can be integrated into a one-stop standardized transaction solution according to the transaction standard.
Multilingual solution standardization
Ali microservice DNS is the best practice in the Java field.
Dubbo+Nacos+Spring-cloud-alibaba/Sentinel/Seata
Of course, in the past year, we have completed the layout of multi-language ecology, including seamless support for service grid/Dapr ecology/Golang ecology, so that all languages can enjoy the dividends of cloud-native microservices.
Service Mesh Technology Returns to Rationality
In 2020, 27% of companies are using service mesh in production (a 50% increase from 2019), while 23% of companies are currently evaluating service mesh technology (cited by CNCF), compared to the popularity of previous years , which is comparable to the overall growth rate of microservices, the service grid is gradually returning to rationality, and users are trying more in multilingual scenarios and new business fields.
Cloud-native gateway gradually takes shape
In 2020, 37% of Ingress implementations choose Envoy (an increase of 116% over 2019), and a large number of companies build next-generation gateway technologies based on Envoy (cited by CNCF).
As Kubernetes standardizes the gateway through Ingess, Ingress is used as the connection point of containers and microservices, and Istio is used as the control to aggregate Kubernetes downwards, and Nacos multiple services to control Ingress (Edge) / Sidecar (Runtime) east-west, north-south, and north-south traffic.
As Ingress standardizes gateways, gateways show a trend of highly integrated development. As a next-generation gateway, cloud-native gateways combine traffic gateways and business gateways into one, reducing resource costs by 50%; integrated security capabilities establish a security line of defense from the entrance; integrated service governance and Observability, improve the high availability of the entire website from the entrance; support single application, Nacos, Kubernetes, Serverless multiple service discovery sources, unified access, unified authentication login.
Summarize
With the sharp decline in the technical threshold of microservices, the accelerated pace of digital upgrading of enterprises, and the rapid development of cloud computing, microservices will be ubiquitous; with the gradual improvement of industry maturity and the promotion of open source and standards, the Standards are gradually formed, and the formation of standards will further help the development of the microservice industry. The future is promising, because I believe, so see!
Article source Alibaba middleware, respect creation! Follow my code forum to learn more...