Brief introduction
Ocelot is implemented in a .NET Core and open source API Gateway, it is powerful, including: routing, aggregation request, service discovery, authentication, authorization, limiting fuse, and built-in load balancer and Service Fabric, Butterfly Tracing integrated. These functions only require only a simple configuration can be completed.
Chart
Ocelot's goal is to use the .NET runtime service-oriented architecture micro / services, to have a unified entry point into their system.
In particular, it is very easy to integrate IdentityServer and bearer tokens.
Ocelot is arranged in a particular order set middleware.
The operation Ocelot HttpRequest object configured to specify a state request to build until it reaches the middleware, the middleware, it creates a HttpRequestMessage object for downstream service request. Ocelot is requesting middleware pipeline last thing. It does not call the next middleware. Service response from the downstream storage and retrieved when requested in each return duct Ocelot store request range. There is a middleware to map HttpResponseMessage to HttpResponse object and returned to the client. Basically it has many other features.
The following is the configuration used when deploying Ocelot.
Basically
Integrated IdentityServer
Multiple instances
Use Consul
Use Service Fabric
