Two quick posts put Postgres at the center of how people think about event data and durable workflows. POST 1 proclaims, "Events are great – I will save them in Postgres instead" [1]. POST 2 outlines a "Durable execution workflow system based on Postgres" [2].
What these posts advocate POST 1 argues for treating events as first-class data in Postgres [1]. POST 2 presents a durable workflow system built on Postgres [2].
Implications to weigh This setup prompts a broader debate: can a general-purpose DB cover the needs of event data and durable workflows, or do you reach for specialized event stores? The questions include performance, tooling, and overall complexity when using Postgres for these workloads [1][2].
Balancing the trade-offs If teams value a single stack and familiar tooling, a Postgres-centric approach can be appealing. However, the posts imply you should watch for ecosystem maturity and potential gaps in event-store features when using a general-purpose DB [1][2].
Closing thought The core takeaway: 2025 discussions are less about a single tool doing everything and more about aligning your stack with team skills and the maturity of the surrounding tooling.
ReferencesReferenced posts: [1] POST ID: 1 [2] POST ID: 2
References
Events are great – I will save them in Postgres instead
Advocates using Postgres to store events; supports PostgreSQL as preferred database for event data.
View sourceDurable execution workflow system based on Postgres
Postgres-based durable workflow system for reliable task execution, described in the Absurd project (GitHub link).
View source