About

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!

Features

A concise list of Ocelot's capabilities, for further details refer to Documentation

• Routing
• Request Aggregation
• GraphQL ¹
• Service Discovery ²
• Service Fabric
• Kubernetes
• Websockets
• Authentication
• Authorization
• Rate Limiting
• Caching
• Quality of Service ³
• Load Balancer
• Logging / Tracing / Correlation
• Headers / Method / Query String / Claims Transformation
• Custom Middleware / Delegating Handlers
• Configuration / Administration REST API
• Platform & Cloud Agnostic Building

Install

Ocelot is designed to work with ASP.NET Core and it targets net8.0 LTS and net9.0 STS target framework monikers (TFMs). ⁴

Install Ocelot package and its dependencies using NuGet package manager:

Install-Package Ocelot

Or via the .NET CLI:

dotnet add package Ocelot

All versions are available on NuGet.

Documentation

• RST-sources: This includes the source code of the documentation as .rst-files, which are up to date for current development.
• Read the Docs: This includes a lot of information and will be helpful if you want to understand the features Ocelot currently offers.
• Ask Ocelot Guru: It is an Ocelot-focused AI designed to answer your questions. ⁵

Coming up

You can see what we are working on in the backlog.

Contributing

We love to receive contributions from the community, so please keep them coming. Pull requests, issues, and commentary welcome!

Please complete the relevant template for issues and pull requests. Sometimes it's worth getting in touch with us to discuss changes before doing any work in case this is something we are already doing or it might not make sense. We can also give advice on the easiest way to do things

Finally, we mark all existing issues as . ⁶ If you want to contribute for the first time, we suggest looking at a

Notes

Footnotes

1. Ocelot does not directly support GraphQL. Developers can easily integrate the GraphQL for .NET library. ↩

2. Ocelot supports Consul, Netflix Eureka, Service Fabric service discovery providers, as well as special modes like Dynamic Routing and Custom Providers. ↩

3. Retry policies only via Polly library. ↩

4. Starting with version 21.0, the solution's code base supports Multitargeting as SDK-style projects. It should be easier for teams to migrate to the currently supported .NET 8 and 9 frameworks. Also, new features will be available for all .NET SDKs that we support via multitargeting. Find out more here: Target frameworks in SDK-style projects ↩

5. Ocelot Guru is an unofficial tool to get answers regarding Ocelot: please consider it an advanced search tool. Thus, we have an official Questions & Answers category in the Discussions space. ↩

6. See all labels for the repository, which are useful for searching and filtering. ↩