Shulou(Shulou.com)06/03 Report--

Guide reading

At present, the container ecology based on Kubernetes is gradually improving, in which three independent projects of Kubernetes, Istio and Knative are mentioned by more and more people, and have begun to try large-scale landing practice, which just constitute the future jigsaw puzzle of the container cloud. Today I would like to share with you what problems these three projects have solved and why they have become a blockbuster.

As the concept of micro-service continues to take root in the hearts of the people, more and more enterprises gradually transform their applications from monomer to micro-service architecture. The emergence of Container container technology just accelerates this transfer process, because it effectively solves the problem of rapid deployment of N-multi-services. However, with the increase in the number of services, more and more enterprises hope to effectively "aggregate" related services together to facilitate unified deployment and management. The emergence of Kubenretes just solves the challenge of large-scale micro-service orchestration and deployment, and makes the whole industry realize that the landing of PaaS can become a reality.

With the increasing number of services under the micro-service system, service operation and maintenance has become an inevitable problem to be solved, so the implementation strategy based on the separation of network agent and control appears in Istio, which allows effective and reasonable control of service control strategy.

It seems to have reached a wonderful stage here:

Micro-service: solve the problem of application cohesion and bloated.

Container: solve the problem of uniform running environment and deployment of services.

Kubernetes: solve the problem of effective "aggregation" deployment of a large number of microservices.

Istio: solve a series of governance problems faced by service online.

At first glance, building a container cloud seems to have a complete link and solution, and everything will be "perfect".

Now let's go back and take an in-depth analysis of whether there is a problem with service interaction under the micro-service system.

First of all, both http and rpc are essentially remote calls of services and services. In developing applications, there is no way to make services transparent to each other. This will lead to a problem: no matter how "fine" the micro-service business is split, it is essentially impossible for business units to operate and develop independently. At the same time, for the derivation of different development fields, it is impossible to choose the most appropriate way of implementation. Therefore, we hope to be able to standardize the development environment based on different "template" + "configuration" ways, while providing "event" mechanism to minimize the coupling between service and service interaction.

Secondly, the dynamic scaling problem of running on the service line. Auto scaling in the current kubernetes environment requires customers to collect monitoring data and implement it manually, but we prefer to be more automated and intelligent on the service line.

Finally, the issue of service standardization. We want the model inside the service to be standard, which can be copied and built quickly; the service communication is standard: protocol standard, format standard; the running environment is standard: rapid deployment, rapid migration.

The emergence of Knative just solves the problems of remote direct call, automatic management of service line and some column standardization.

Let's take a look at the relationship between the three:

Kubernetes and Istio I believe you are more familiar with, here do not do too much introduction, students in need can pay attention to our previous release of related articles, here we focus on Knative.

Knative is Google's open source serverless architecture, which aims to provide an easy-to-use serverless solution to standardize serverless. At present, the main participating companies are Google, Pivotal, IBM and Red Hat, which were released in July 2018 and are currently in the stage of rapid development.

Knative composition

Build

Construction system: build user-defined applications into container images, standardize construction for kubernetes, which is different from Dockerfile image construction, and focus on solving the standardization of kubernetes environment construction.

Serving

Service system: use some of the functions of Istio to configure application routing, upgrade and auto scaling. Serving includes container lifecycle management, container periphery object (service,ingres) generation (properly unifying service instances with access), monitoring application requests, automatically resilient load, and configuring service access rules using Virtual service and destination. Only in this way can we ensure the consistency of service presentation and the automatic management of service operation.

Eventing

Event system: used to automatically complete the binding and trigger of events. The biggest difference between an event system and a direct call is the responsive design, which allows the service itself to run without shielding the relationship between the caller and the callee. As a result, the rapid aggregation of business can be achieved at the business level, and may provide events for subsequent business choreography innovation.

Now let's focus on the application service life cycle from a different perspective:

Knative solution application template + standardized construction scenario for unified environment

Kubernetes as an infrastructure to solve application orchestration and running environment scenarios

As the communication infrastructure layer, Isito ensures that the application service runs detectable, configurable and traceable problems.

These three factors run through the whole life cycle of application services, and container cloud is also the control platform for managing application services, which can well explain why Kubernetes,Istio,Knative will become the troika for building container cloud in the future.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.