Gravtory: durable Python workflows without a message broker
Published: (April 16, 2026 at 02:33 PM EDT)
1 min read
Source: Dev.to
Source: Dev.to
Most workflow libraries require you to run an additional service.
Celery needs Redis, Temporal needs its own server, and so on. Gravtory leverages the database you already have, eliminating the need for a separate message broker.
What a saga looks like
A typical saga can be found in the repository:
https://github.com/vatryok/Gravtory
If the process crashes mid‑saga, Gravtory automatically resumes from the last checkpoint—no data loss and no manual recovery required.
Demo
Watch a short demonstration of Gravtory in action:
Additional links
- Author’s GitHub: https://github.com/vatryok
