- Notifications
You must be signed in to change notification settings - Fork1.7k
ThreeMammals/Ocelot
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
Ocelot is a .NET API Gateway. This project is aimed at people using .NET running a microservices / service-oriented architecturethat need a unified point of entry into their system. However it will work with anything that speaks HTTP(S) and run on any platform that ASP.NET Core supports.
In particular we want easy integration withIdentityServer reference andBearer tokens.We have been unable to find this in our current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens.We would rather use the IdentityServer code that already exists to do this.
Ocelot is a bunch of middlewares in a specific order.
Ocelot manipulates theHttpRequest
object into a state specified by its configuration until it reaches a request builder middleware, where it creates aHttpRequestMessage
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 requests goes back up the Ocelot pipeline.There is a piece of middleware that maps theHttpResponseMessage
onto theHttpResponse
object and that is returned to the client.That is basically it with a bunch of other features!
A quick list of Ocelot's capabilities, for more information see theDocumentation.
- Routing
- Request Aggregation
- GraphQL1
- Service Discovery2
- Service Fabric
- Kubernetes
- Websockets
- Authentication
- Authorization
- Rate Limiting
- Caching
- Quality of Service3
- Load Balancer
- Logging /Tracing /Correlation
- Headers /Method /Query String /Claims Transformation
- Custom Middleware /Delegating Handlers
- Configuration /Administration REST API
- Platform & Cloud AgnosticBuilding
Ocelot is designed to work with ASP.NET Core and it targetsnet6.0
,net7.0
andnet8.0
frameworks.4
InstallOcelot package and its dependencies using NuGet Package Manager:
Install-Package Ocelot
Or via the .NET CLI:
dotnet add package Ocelot
All versions can be foundon nuget.
- Ocelot documentation — Read the Docs
This includes lots of information and will be helpful if you want to understand the features Ocelot currently offers. - Ocelot RST Docs
This includes source code of documentation as.rst files which are up to date for current development. - Ask Ocelot Guru
It's a Ocelot-focused AI to answer your questions.
You can see what we are working on inbacklog.
We love to receive contributions from the community, so please keep them coming
Pull requests, issues and commentary welcome!
Please complete the relevanttemplate forissues andPRs.Sometimes it's worth getting in touch with us todiscuss 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.5
If you want to contribute for the first time, we suggest looking at a
Footnotes
Ocelot doesn’t directly supportGraphQL. Developers can easily integrate theGraphQL for .NET library.↩
Ocelot does supportConsul,Netflix Eureka,Service Fabric service discovery providers, and special modes likeDynamic Routing andCustom Providers.↩
Starting withv21.0, the solution's code base supportsMultitargeting as SDK-style projects. It should be easier for teams to move between (migrate to) .NET 6, 7 and 8 frameworks. Also, new features will be available for all .NET SDKs which we support via multitargeting. Find out more here:Target frameworks in SDK-style projects↩
About
.NET API Gateway