mart-w/kanidm
1
0
Fork 0
mirror of https://github.com/kanidm/kanidm.git synced 2025-02-23 20:47:01 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update images

Browse source
This commit is contained in:
William Brown 2019-11-04 14:09:54 +10:00
parent 91ba26d0ee
commit 516a128c5f
1 changed files with 4 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
designs/architecture.rst
View file

@ -44,9 +44,8 @@ Search
Search is the "hard worker" of the server, intended to be a fast path with minimal overhead
so that clients can acquire data as quickly as possible. The server follows the below pattern.
<p align="center">
<img src="https://raw.githubusercontent.com/Firstyear/kanidm/master/designs/diagrams/search-flow.png" width="80%" height="auto" />
</p>
.. image:: diagrams/search-flow.png
:width: 800
1. All incoming requests are from a client on the left. These are either REST requests, or a structured
protocol request via the raw interface. It's interesting to note the raw request is almost identical
@ -103,9 +102,8 @@ Write
The write path is similar to the search path, but has some subtle differences that are
worth paying attention to.
<p align="center">
<img src="https://raw.githubusercontent.com/Firstyear/kanidm/master/designs/diagrams/write-flow.png" width="80%" height="auto" />
</p>
.. image:: diagrams/write-flow.png
:width: 800
1., 2. Like search, all client operations come from the REST or raw apis, and are transformed or
generated into messages. These messages are sent to a single write worker. There is only a single