Practical MQTT patterns
Guides
Clear choices for replay, current state, queued work, and durable storage at the edge.
Choose the smallest MQTT durability model that tells the truth about your data.
These guides start with operational problems, offline consumers, current state, queued work, and constrained edge machines, then connect each one to the relevant part of Sagüin's design and its runnable examples.
Latest, append and queue channels
How Sagüin’s three channel types differ from retained messages, persistent sessions and shared subscriptions, what operators control, and how to produce and consume with MQTT, saguin-python and saguin-js.
Read guideReplay MQTT messages after an outage
Learn how MQTT session queues differ from a replayable log, and how Sagüin resumes each durable consumer from a stored position.
Read guideBuild a durable MQTT work queue
Use MQTT topics as a work queue with application acknowledgements, retries, visibility timeouts, and dead-letter handling for edge workers.
Read guideRetained messages or replay?
Compare retained messages, persistent sessions, latest-value state, and replayable logs so each MQTT workload uses the right durability model.
Read guideRun durable MQTT state on SQLite
See when one MQTT broker and one SQLite database are a practical fit for durable messaging on a small edge machine.
Read guide