{"slug": "dbos", "name": "DBOS", "category": "infra", "category_name": "Infrastructure and DevOps", "description": "", "recommenders": 3, "commenters": 5, "warners": 1, "score": 1.936, "rising": -0.98, "first": "2025-11-13", "latest": "2026-09-14", "why": "I love the product and what you are doing -- it's definitely needed and valuable.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 1, "compare": 0, "warn": 1}, "spark": [1, 0, 0, 0, 1, 0, 1, 0, 0, 0, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "I love the product and what you are doing -- it's definitely needed and valuable.", "icon": true, "domain": null, "github_repo": "github.com/dbos-inc/dbos-transact-golang", "official_url": "https://www.dbos.dev", "pricing": "", "aliases": ["DBOS"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 773046402, "item_id": 48315400, "url": "https://news.ycombinator.com/item?id=48315400", "by": "saxenaabhi", "date": "2026-05-28", "stance": "recommend", "quote": "Where DBOS absolutely shines is", "excerpt": "As someone who uses dbos.dev, restate.dev, cf workflows here is a snippet from our Agents.md We use durable execution a lot since we are handling payments/orders. For durable execution right now we are using - 1. **Restate.dev** for payment integrations on northflank since its faster than cf workflows, independent of cf and its downtime and self-hostable vendor-lock-in free, - 2. **Cloudflare workflows** for non crit", "context": "handles payments/orders", "use_case": "atomic messaging with Postgres transactions", "switched_from": "", "story": "Just Use Postgres for Durable Workflows"}, {"id": 757289152, "item_id": 47330572, "url": "https://news.ycombinator.com/item?id=47330572", "by": "jedberg", "date": "2026-03-10", "stance": "recommend", "quote": "If you\u2019re already running Postgres, check out DBOS[0].", "excerpt": "It\u2019s a real problem you\u2019re solving but the good news is that it\u2019s already solved! You don\u2019t have to build it yourself. You\u2019re looking for durable execution to solve your problem. If you\u2019re already running Postgres, check out DBOS[0]. It turns your app into its own durable executor using your database for coordination. [0] https://github.com/dbos-inc/dbos-transact-golang", "context": "", "use_case": "durable execution for background jobs", "switched_from": "", "story": "Ask HN: Do you still run Redis and workers just for background jobs?"}, {"id": 734767216, "item_id": 45922951, "url": "https://news.ycombinator.com/item?id=45922951", "by": "ibgeek", "date": "2025-11-13", "stance": "recommend", "quote": "I love the product and what you are doing -- it's definitely needed and valuable.", "excerpt": "I really wish you guys would change the name since the product has moved so far away from the goals and concepts in the original publication. :). I love the product and what you are doing -- it's definitely needed and valuable.", "context": "", "use_case": "durable workflows", "switched_from": "", "story": "Show HN: DBOS Java \u2013 Postgres-Backed Durable Workflows"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 779256545, "item_id": 48703534, "url": "https://news.ycombinator.com/item?id=48703534", "by": "aliasxneo", "date": "2026-06-27", "stance": "warn", "quote": "I wasn\u2019t convinced I wouldn\u2019t get rug pulled by a VC backed company", "excerpt": "I recently needed an OSS durable execution engine and chose River (I use Go) over DBOS because I wasn\u2019t convinced I wouldn\u2019t get rug pulled by a VC backed company. Both are technically commercial, but River seemed to be doing a lot more OSS friendly moves lately than DBOS, and AFAIK they are self bootstrapped.", "context": "", "use_case": "durable execution engine", "switched_from": "", "story": "Show HN: DBOSify \u2013 Drop-in Temporal replacement built on Postgres"}]}], "who": [{"by": "saxenaabhi", "context": "handles payments/orders", "url": "https://news.ycombinator.com/item?id=48315400", "date": "2026-05-28"}], "tags": [], "use_cases": ["durable execution", "durable execution engine", "atomic messaging with postgres transactions", "durable execution for background jobs", "durable workflows"], "compared": [{"slug": "restate", "name": "Restate", "co": 4, "switched_from": 0, "switched_to": 0}, {"slug": "temporal", "name": "Temporal", "co": 3, "switched_from": 0, "switched_to": 0}, {"slug": "cloudflare-workflows", "name": "Cloudflare Workflows", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [{"id": 734843472, "item_id": 45927717, "url": "https://news.ycombinator.com/item?id=45927717", "by": "KraftyOne", "date": "2025-11-14", "stance": "recommend", "quote": "DBOS implements a simpler library-based architecture where each of your processes independently \"pulls\" from a database queue.", "excerpt": "The Restate model depends on a long-running external orchestrator to do the \"pushing\". However, that comes with downsides--you have to operate that orchestrator and its data store in production (and it's a single point of failure) and you have to rearchitect your application around it. DBOS implements a simpler library-based architecture where each of your processes independently \"pulls\" from a database queue. To mak", "context": "DBOS team member", "use_case": "durable workflows", "switched_from": "", "story": "Show HN: DBOS Java \u2013 Postgres-Backed Durable Workflows"}], "threads": [{"url": "https://news.ycombinator.com/item?id=45920156", "title": "Show HN: DBOS Java \u2013 Postgres-Backed Durable Workflows", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=49696335", "title": "Temporal raises $550M at a $12.55B valuation", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48662988", "title": "Show HN: DBOSify \u2013 Drop-in Temporal replacement built on Postgres", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48313530", "title": "Just Use Postgres for Durable Workflows", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47320768", "title": "Ask HN: Do you still run Redis and workers just for background jobs?", "mentions": 1}], "sentiment_by_month": {"2025-11": {"recommend": 1}, "2025-12": {}, "2026-01": {}, "2026-02": {}, "2026-03": {"recommend": 1}, "2026-04": {}, "2026-05": {"recommend": 1}, "2026-06": {"warn": 1}, "2026-07": {}, "2026-08": {}, "2026-09": {"neutral": 1}, "2026-10": {}}, "quotes": [{"id": 795178976, "item_id": 49698686, "url": "https://news.ycombinator.com/item?id=49698686", "by": "drdexebtjl", "date": "2026-09-14", "stance": "neutral", "quote": "I think it\u2019s nice that it\u2019s just an SDK and a Postgres database, but they don\u2019t have SDKs for the languages we use at work.", "excerpt": "I think it\u2019s nice that it\u2019s just an SDK and a Postgres database, but they don\u2019t have SDKs for the languages we use at work.", "context": "", "use_case": "durable execution", "switched_from": "", "story": "Temporal raises $550M at a $12.55B valuation"}, {"id": 779256545, "item_id": 48703534, "url": "https://news.ycombinator.com/item?id=48703534", "by": "aliasxneo", "date": "2026-06-27", "stance": "warn", "quote": "I wasn\u2019t convinced I wouldn\u2019t get rug pulled by a VC backed company", "excerpt": "I recently needed an OSS durable execution engine and chose River (I use Go) over DBOS because I wasn\u2019t convinced I wouldn\u2019t get rug pulled by a VC backed company. Both are technically commercial, but River seemed to be doing a lot more OSS friendly moves lately than DBOS, and AFAIK they are self bootstrapped.", "context": "", "use_case": "durable execution engine", "switched_from": "", "story": "Show HN: DBOSify \u2013 Drop-in Temporal replacement built on Postgres"}, {"id": 773046402, "item_id": 48315400, "url": "https://news.ycombinator.com/item?id=48315400", "by": "saxenaabhi", "date": "2026-05-28", "stance": "recommend", "quote": "Where DBOS absolutely shines is", "excerpt": "As someone who uses dbos.dev, restate.dev, cf workflows here is a snippet from our Agents.md We use durable execution a lot since we are handling payments/orders. For durable execution right now we are using - 1. **Restate.dev** for payment integrations on northflank since its faster than cf workflows, independent of cf and its downtime and self-hostable vendor-lock-in free, - 2. **Cloudflare workflows** for non crit", "context": "handles payments/orders", "use_case": "atomic messaging with Postgres transactions", "switched_from": "", "story": "Just Use Postgres for Durable Workflows"}, {"id": 757289152, "item_id": 47330572, "url": "https://news.ycombinator.com/item?id=47330572", "by": "jedberg", "date": "2026-03-10", "stance": "recommend", "quote": "If you\u2019re already running Postgres, check out DBOS[0].", "excerpt": "It\u2019s a real problem you\u2019re solving but the good news is that it\u2019s already solved! You don\u2019t have to build it yourself. You\u2019re looking for durable execution to solve your problem. If you\u2019re already running Postgres, check out DBOS[0]. It turns your app into its own durable executor using your database for coordination. [0] https://github.com/dbos-inc/dbos-transact-golang", "context": "", "use_case": "durable execution for background jobs", "switched_from": "", "story": "Ask HN: Do you still run Redis and workers just for background jobs?"}, {"id": 734767216, "item_id": 45922951, "url": "https://news.ycombinator.com/item?id=45922951", "by": "ibgeek", "date": "2025-11-13", "stance": "recommend", "quote": "I love the product and what you are doing -- it's definitely needed and valuable.", "excerpt": "I really wish you guys would change the name since the product has moved so far away from the goals and concepts in the original publication. :). I love the product and what you are doing -- it's definitely needed and valuable.", "context": "", "use_case": "durable workflows", "switched_from": "", "story": "Show HN: DBOS Java \u2013 Postgres-Backed Durable Workflows"}]}