oxeo0/opsec-blogposts
1
0
Fork 0
mirror of http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/opsec-blogposts.git synced 2025-06-08 05:19:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix stuff

Browse source
This commit is contained in:
nihilist 2025-05-29 19:03:51 +02:00
parent 7739e73322
commit 9a415258f4
84 changed files with 313 additions and 191 deletions
Download patch file Download diff file Expand all files Collapse all files

2
onionbalancelb/index.md
View file

@ -14,6 +14,8 @@ tags:
## **Introduction**
![](../context/sensitive_remote.png)
In our [last tutorial](../mysqlmastermaster/index.md), after setting up database replication between two instances of our vegetable shop, you might be wondering if there's a way for clients to access the service via a single frontend. Practically, this means users will go to your main onion v3 URL and may be presented with different backend instances in a transparent manner.
When one backend instance becomes unavailable, users will still be able to access the service on other backends. After the unavailable backend comes back online, changes made during its offline period will be automatically replicated to the database. It will also resume participating in load balancing.