mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-08 23:50:43 +02:00
Updated Seaweed Message Queue (markdown)
+6
-6
@@ -14,10 +14,10 @@ The structured messages are published to message brokers, persisted to SeaweedFS
|
||||
The Agent can be run either on the server side, or as a sidecar on each client.
|
||||
|
||||
# Features
|
||||
* Structured Messages: SeaweedFS is to store unstructured data files. Seaweed Message Queue is to store structured messages.
|
||||
* The messages stored on SeaweedFS can be converted into Parquet files, saving disk spaces with more efficient columnar compression.
|
||||
* The Parquet files can be consumed in streams via Seaweed messaging brokers.
|
||||
* The Parquet files can be read in batches directly via SeaweedFS.
|
||||
* Message published successfully are acknowledged, or receive an error if not successful.
|
||||
* Structured Messages: SeaweedFS is used to store unstructured data files, while Seaweed Message Queue is used to store structured messages.
|
||||
* Messages stored in SeaweedFS can be converted into Parquet files, saving disk space with more efficient columnar compression.
|
||||
* The messages in Parquet files can be streamed via Seaweed messaging brokers.
|
||||
* The Parquet files can be read in batches directly from SeaweedFS.
|
||||
* Messages published successfully are acknowledged, while unsuccessful ones receive an error.
|
||||
* Message consume offsets are tracked and persisted.
|
||||
* Consumer APIs can process messages in multi-threads while still ensuring serial processing the same message key.
|
||||
* Consumer APIs can process messages in multiple threads while still ensuring serial processing of messages with the same key.
|
||||
|
||||
Reference in New Issue
Block a user