eosswedenorg/thalos-docs
1
0
Fork 0
mirror of https://github.com/eosswedenorg/thalos-docs synced 2026-08-31 21:08:15 +02:00
Code Releases Activity

minor style fixes

Browse source
This commit is contained in:
Henrik Hautakoski 2024-08-29 14:53:35 +02:00
parent 781da3b6a8
commit d564a0b3ee
5 changed files with 28 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/architecture/index.md
View file

@ -37,7 +37,10 @@ However, these advantages can also be considered drawbacks in certain situations
- **Immediate message consumption**: Pub/Sub requires subscribers to consume messages immediately upon publication. If a client is unable to read a message promptly, it is discarded.
In contrast, Streams in Redis provide built-in message persistence. Messages are stored as entries in the stream and can be consumed at any time, even if they were published before the subscriber connected.
In contrast, Streams in Redis provide built-in message persistence.
Messages are stored as entries in the stream and can be consumed at any time, even if they were published before the subscriber connected.
This feature addresses the drawbacks of immediate message consumption and message loss associated with Pub/Sub.
Currently, Streams are not implemented in Thalos. However, there are plans to consider implementing Streams in the future, based on the demand for such functionality. It's important to note that Streams introduce additional complexity to the client implementation.
Currently, Streams are not implemented in Thalos.
However, there are plans to consider implementing Streams in the future, based on the demand for such functionality.
It's important to note that Streams introduce additional complexity to the client implementation.