From 9056042c352637811a6caf14ae358cc7151e2f87 Mon Sep 17 00:00:00 2001 From: Peter Taoussanis Date: Thu, 30 May 2024 09:02:44 +0200 Subject: [PATCH] [doc] [#309] Add max message size to message queue docs (@sanguivore-easyco) --- wiki/3-Message-queue.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/wiki/3-Message-queue.md b/wiki/3-Message-queue.md index bb8e8c6..7f7b0d8 100644 --- a/wiki/3-Message-queue.md +++ b/wiki/3-Message-queue.md @@ -56,4 +56,5 @@ The following semantics are provided: - Messages are **handled once and only once**. - Messages are **handled in loose order** (exact order may be affected by the number of concurrent handler threads, and retry/backoff features, etc.). - Messages are **fault-tolerant** (preserved until acknowledged as handled). -- Messages support optional per-message **de-duplication**, preventing the same message from being simultaneously queued more than once within a configurable per-message backoff period. \ No newline at end of file +- Messages support optional per-message **de-duplication**, preventing the same message from being simultaneously queued more than once within a configurable per-message backoff period. +- Messages are serialized with [Nippy](https://www.taoensso.com/nippy) and stored as [byte strings](https://redis.io/docs/latest/develop/data-types/strings) in Redis hashes, so each serialized message has a **maximum size of 512MiB**. You'll normally want to use *much* smaller messages though (typically small maps or UUIDs/pointers to larger data stores when necessary). \ No newline at end of file