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

This article shows you how to implement Ocelot in the ASP.NET Core micro-service architecture, which is concise and easy to understand, which will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

Microservices Architecture is an architectural style, in which a large and complex software application consists of one or more micro services. Each micro-service in the system can be deployed independently, and each micro-service is loosely coupled. Each microservice focuses only on completing a task and accomplishing that task well. In all cases, each task represents a small business capability.

As the attention of .NET Core continues to rise, .NET Core is more and more used in micro-services and cloud native application development. Taking .NET Core as an example, it is hot to use ocelot+consul to automatically complete service registration (Consul) and service discovery (ocelot reads services in Consul) by embedding ocelot and consul clients in the service. When a user accesses a url, the ocelot will forward the user's request to the real service pulled from the Consul according to the route Ocelot as an open source API gateway development library under the .NET Core platform is more and more recognized by the community, and there are many cases of application in production, so the concepts of API gateway and service registration and discovery are more important in micro services, so let's familiarize ourselves with Ocelot as an API gateway component today.

Why Micro Services Architecture uses API Gateway

What is Ocelot?

Environment preparation (registering API services with Consul through configuration files) Ocelot practice of ASP.NET Core micro-services architecture

1), the function of API gateway

The API gateway is the only entry to the service of a requesting system. From the perspective of object-oriented design, it is similar to the appearance pattern. The API gateway encapsulates the internal architecture of the system and provides a customized API for each client. It may also have other responsibilities, such as authentication, monitoring, load balancing, caching, request fragmentation and management, and static response processing.

The core point of the API gateway approach is that all clients and consumers access micro-services through a unified gateway and handle all non-business functions at the gateway layer. Gateway has its own definition in hardware and its own interpretation in software architecture. It is the entrance of all requests. Requests are called to the gateway, processed and processed, and then returned to the client. This process is, of course, the core of the gateway and the core of Ocelot. We can implement user authorization, verification, cache, authentication and many other concerns in the gateway!

2) about the choice of API gateway?

API gateways are open source (Kong, etc.) and commercial enterprise-level gateways, which are generally better than open source ones in terms of ease of use and scalability. At present, for the choice of gateways in .net Core, we recommend using Ocelot developed in C # language. Finally: API gateways are usually used in conjunction with service registration and discovery software to complement each other.

The above is how to implement Ocelot in the ASP.NET Core micro-service architecture. Have you learned the knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

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.