add simpler diagram for onionbalance

This commit is contained in:
oxeo0 2025-02-26 11:58:51 +01:00
parent 774e2fe217
commit 7ef6e621b3
3 changed files with 12 additions and 3 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

View file

Before

Width:  |  Height:  |  Size: 243 KiB

After

Width:  |  Height:  |  Size: 243 KiB

Before After
Before After

View file

@ -101,15 +101,24 @@ When one backend instance becomes unavailable, users will still be able to acces
</p>
<p>
At the end of this guide, we'll have a load-balanced frontend URL available to users. Here's a diagram illustrating the desired result:
At the end of this guide, we'll have a load-balanced frontend URL. There is simplified diagram of how this works:
</p>
<img src="1.png" class="imgRz">
<img src="1.0.png" class="imgRz">
<br><br>
<p>
From an end user's perspective accessing our store:
User accessing the frontend gets transparently redirected to either of the backends.<br><br>
A more detailed version presenting how clients get connected to the load-balanced service over Tor:
</p>
<img src="1.1.png" class="imgRz">
<br><br>
<p>
From an end user's perspective:
<ul>
<li><b>1</b> - Tor client makes a request to the Distributed Hash Table (DHT) with the address of vegetable shop.</li><br>
<li><b>2</b> - The DHT returns a descriptor with multiple backend addresses. Tor client chooses one of the addresses.</li><br>