.NET API Gateway
Ocelot is a .NET API gateway. This project is aimed at people using .NET running a microservices (service-oriented) architecture that needs a unified point of entry into their system. However, it will work with anything that speaks HTTP(S) and runs on any platform that ASP.NET Core supports.
Ocelot consists of a series of ASP.NET Core middlewares arranged in a specific order.
Ocelot custom middlewares manipulate the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware, where it creates a HttpRequestMessage object, which is used to make a request to a downstream service.
The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware.
The response from the downstream service is retrieved as the request goes back up the Ocelot pipeline.
There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object, and that is returned to the client.
That is basically it, with a bunch of other features!
Ocelot is designed to work with ASP.NET Core and it targets net9.0 STS and net8.0, net10.0 LTS target framework monikers (TFMs). [^1]
Install Ocelot package and its dependencies using the .NET CLI:
dotnet add package Ocelot
All versions are available on NuGet.
The primary features—Configuration and Routing—are always utilized by users, even in a minimal app setup, without customizations or extra configurations. Ocelot's capabilities are categorized into three main groups of features: solid, hybrid, and feature-family groups, which are explained below.
Feature groups are explained in the table below
Feature Relationships and Notes Administration Administration heavily depends on Authentication, and Administration API methods are part of Authentication, Caching, and Configuration Aggregation[^4] Aggregation relies on Routing Authentication Authentication followed by Authorization Configuration Configuration depends on Dependency Injection, includingGET/POST operations via the Administration REST API, a specialized Websockets scheme/protocol, advanced Middleware Injection, and Metadata-based extensions
Routing
Routing offers specialized Websockets and Dynamic Routing modes but does not support GraphQL[^6]
Load Balancer
Load Balancer is a critical dependency for Service Discovery
Logging
Logging includes Error Handling and Tracing
Service Discovery[^5]
Service Discovery with the following discovery providers: Consul, Kubernetes, Eureka, and Service Fabric
Transformations
They provide transformations for Claims, Headers, and Method
Ocelot customizations can be configured using Metadata, developed with Delegating Handlers, and in advanced scenarios, they can be developed and then configured with Middleware Injection. For further details, refer to the Documentation.
Stay updated with the latest releases of Ocelot and its extension packages from the ThreeMammals organization. This section provides a snapshot of release status across the entire Ocelot ecosystem.
Project Latest Release Pre-Release (beta) Release Date [](https://www.nuget.org/packages/Ocelot.QualityOfService.Polly "Ocelot.QualityOfService.Polly beta version packagNo open issues yet, or sync has not completed.