tk/Ocelot
1
0
Fork 0
mirror of https://github.com/nsnail/Ocelot.git synced 2025-06-18 21:28:16 +08:00
Code Issues Packages Projects Releases Wiki Activity

images for docs

Browse Source
This commit is contained in:
Tom Gardham-Pallister
2017-12-04 09:03:49 +00:00
parent df03e2b51a
commit e12b9d123e
6 changed files with 36 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
docs/introduction/bigpicture.rst
View File

@ -1,4 +1,38 @@
Big Picture
===========
Coming soon...
Ocleot is aimed at people using .NET running
a micro services / service orientated architecture
that need a unified point of entry into their system.
In particular I want easy integration with
IdentityServer reference and bearer tokens.
Ocelot is a bunch of middlewares in a specific order.
Ocelot manipulates 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 stored in a per request scoped repository
and retrived as the requests 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.
The following are configuration that you use when deploying Ocelot.
Basic Implementation
^^^^^^^^^^^^^^^^^^^^
.. image:: images/OcelotBasic.jpg
With IdentityServer
^^^^^^^^^^^^^^^^^^^
.. image:: images/OcelotIndentityServer.jpg
Multiple Instances
^^^^^^^^^^^^^^^^^^
.. image:: images/OcelotMultipleInstances.jpg
With Consul
^^^^^^^^^^^
.. image:: images/OcelotMultipleInstancesConsul.jpg