cx/lobby
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

README update

Browse Source
This commit is contained in:
Adam Štrauch 2021-09-07 00:50:13 +02:00
parent 7010316f8f
commit 2f4203e7c3
Signed by: cx
GPG Key ID: 018304FFA8988F8D
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -39,9 +39,10 @@ your internal system that sends emails and it needs to know where is the SMTP se
example. example.
Lobby doesn't care if you have a one or thousand instances of it running. Each instance Lobby doesn't care if you have a one or thousand instances of it running. Each instance
is connected to a common point which is a [NATS server](https://nats.io/) in this case. NATS is super fast and reliable is connected to a common point which is a [NATS server](https://nats.io/) or Redis. NATS is super fast and reliable
messaging system which handles the communication part but also the high availability part. messaging system which handles the communication part but also the high availability part.
NATS is easy to run and it offloads a huge part of the problem from lobby itself. NATS is easy to run and it offloads a huge part of the problem from lobby itself. But Redis
is not a bad choice either in some cases.
The code is open to support multiple backends and it's not that hard to add a new one. The code is open to support multiple backends and it's not that hard to add a new one.
Support for NATS is only less than 150 lines. Support for NATS is only less than 150 lines.