From the creators of Postgres & Apache Spark -- Build reliable backends effortlessly
Cambridge, MA
- Tweets 1,081
- Following 116
- Followers 1,650
- Likes 1,666
Join us on Nov 12 for the first episode of "Durable Stories" with @qianl_cs from DBOS, @levpgdog from PgDog, and @kelvich from Databricks!
"Postgres, Postgres Everywhere" is an expert panel where we'll gather to discuss how far we can push Postgres before we need something else.
Register here: luma.com/dbos-aola
1
1
9
1,737
Love seeing more projects exploring durable execution directly on Postgres.
Btw this is the same architectural philosophy behind @DBOS_Inc
pgtask: durable tasks and workflows that live entirely in PostgreSQL 🐘
- No broker, no coordinator, no extension
- Enqueue inside your own transaction
- Pydantic AI agents survive crashes with PGTaskDurability
kludex.github.io/pgtask/
2
1
12
709
Help us get to 1 billion workflows/sec next.
We just scaled DBOS to 1M+ workflows/sec
To help our largest users scale, we made DBOS run on sharded Postgres (supporting any sharding engine: PgDog, Citus, Neki, soon Multigres, anything custom…), allowing you to horizontally scale your workflows across many databases.
We found that DBOS scales linearly to 1M workflows/sec sharded across 50 databases. We considered going for more, but the AWS bill from the benchmark servers had become too high
Just published a new blog post about how we built it (and the tricky architectural issues we had to solve to make sharding scale):
👇
1
2
16
917
DBOS retweeted
We just scaled DBOS to 1M+ workflows/sec
To help our largest users scale, we made DBOS run on sharded Postgres (supporting any sharding engine: PgDog, Citus, Neki, soon Multigres, anything custom…), allowing you to horizontally scale your workflows across many databases.
We found that DBOS scales linearly to 1M workflows/sec sharded across 50 databases. We considered going for more, but the AWS bill from the benchmark servers had become too high
Just published a new blog post about how we built it (and the tricky architectural issues we had to solve to make sharding scale):
👇
3
3
14
3,347
DBOS retweeted
A big bang PR to refactor and migrate production agent workflows on @DBOS_Inc , excited about this.
1
3
5
135
Just released DBOS TypeScript 5.4 and Python 3.4!
With this release, we're introducing DBOS Transact Enterprise, a commercial extension of our open-source libraries, with advanced features for operating durable workflows at scale.
Two new Enterprise features in this release:
- Sharded Postgres support: Scale horizontally to millions of durable workflows/sec.
- Automatic workflow version upgrades: Upgrade workflow code without disrupting running workflows.
DBOS Transact Enterprise is included in all paid DBOS plans. Our core DBOS Transact libraries remain open source.
Check out the release notes:
- Python 3.4: github.com/dbos-inc/dbos-tra…
- TypeScript 5.4: github.com/dbos-inc/dbos-tra…
2
2
10
398
DBOS Golang v1.8.0 is also released. It includes the aforementioned auto-upgrade feature. Release notes: github.com/dbos-inc/dbos-tra…
1
68
This will be my first time hosting a fireside chat. Looking forward to it!
I've got some fun topics lined up for Lev and Stas on how far we can push Postgres. If you have any questions you'd like us to cover, drop them in the comments.
Join us on Nov 12 for the first episode of "Durable Stories" with @qianl_cs from DBOS, @levpgdog from PgDog, and @kelvich from Databricks!
"Postgres, Postgres Everywhere" is an expert panel where we'll gather to discuss how far we can push Postgres before we need something else.
Register here: luma.com/dbos-aola
3
3
26
1,457
We're looking to switch our AWS reserved instance types and have quite a bit of m5 capacity available on the marketplace. If you're looking for m5 RIs, feel free to DM me with the specific instance types you need. Happy to see if we can help.
SITUATION DETECTED: Amazon CEO Andy Jassy says that AWS capacity for 2026 is completely sold out, 2027 is largely sold out, and "a good chunk" of 2028 is already sold as well.
1
4
19
2,988
What do financial processing and AI software factories have in common? - Durable workflows
At yesterday's DBOS User Group, we had two great talks from teams building with DBOS:
- Credix: Using DBOS for financial processing
- Cortex: Building an AI software factory powered by durable workflows
Really cool to see durable execution being used for such different use cases.
Catch the recordings here 👇
2
4
7
385
Credix: dbos.dev/webcast/dbos-custom…
Cortex: dbos.dev/webcast/cortex-soft…
2
76
Seeing all these security incidents makes me pretty nervous. It might also explain why more DBOS customers are asking for fully self-hosted and air-gapped deployments these days. Control over your own infrastructure is becoming more important than ever.
1
5
22
997
Yeah we work on the boring persistent server so our users don't have to..
How to keep agent memory intact when execution environments crash or sleep:
Keep the loop itself on a boring persistent server.
Run code execution and bash calls in throwaway Firecracker microVMs.
When an environment is idle, snapshot the microVM and spin it down.
Route interrupts and webhooks directly to the server so nothing drops while the VM is paused.
1
6
745
Durable execution is cool (again)! Great to see Vercel bring durable workflows to more agent harnesses and raise awareness of this concept.
The real challenges remain in running many agents at scale, coordinating them through durable queues, and making efficient use of Postgres (or whatever database you're using).
That's where things get really interesting and I've been spending most of my time on.
Introducing 𝚍𝚞𝚛𝚊𝚋𝚕𝚎-𝚑𝚊𝚛𝚗𝚎𝚜𝚜. Run Pi, OpenCode, Codex, Claude Code, eve, fx, or your own harness durably on Vercel.
With 𝚍𝚞𝚛𝚊𝚋𝚕𝚎-𝚑𝚊𝚛𝚗𝚎𝚜𝚜, agents automatically resume work after failures and run for hours, days, or months. vercel.com/blog/making-every…
1
3
11
798
Just a reminder that our User Group meetup is happening tomorrow. Looking forward to seeing you there!
Join us for the next DBOS User Group Meetup on October 22!
This month, @Credix_finance and Cortex will share how they're using DBOS to build durable workflows for commercial lending and AI software factories. We'll also share the results of our roadmap survey and open the floor for discussion.
As always, there will be plenty of time to connect with fellow DBOS users and our engineering team. We'd love to hear your feedback and ideas!
Register here: luma.com/2f5n3nr1?tk=GZ8SFs
5
269
I always found Webflow hard to navigate (it was a choice from 3 years ago). So my team just migrated the entire DBOS site from Webflow to React, all done by Claude Code. The agent worked on its own for three hours and rebuilt the whole site while preserving the original design.
Now the entire website is just code, and I can finally change anything I want.
8
3
14
764
New releases across DBOS Transact SDKs: TypeScript v5.3, Python v3.3, and Go v1.7.
One important change across all three releases: we moved the DBOS Conductor client into a separate Enterprise package. This change will allow us to deliver several exciting new features in the coming weeks.
If you're only using the open-source DBOS libraries, nothing changes and just upgrade as usual.
If you're using DBOS Conductor or DBOS Cloud, you'll need to install the Enterprise dependency when upgrading:
TypeScript:
𝗇𝗉𝗆 𝗂 @𝖽𝖻𝗈𝗌-𝗂𝗇𝖼/𝖽𝖻𝗈𝗌-𝖾𝗇𝗍𝖾𝗋𝗉𝗋𝗂𝗌𝖾
Python:
𝗉𝗂𝗉 𝗂𝗇𝗌𝗍𝖺𝗅𝗅 𝖽𝖻𝗈𝗌[𝖾𝗇𝗍𝖾𝗋𝗉𝗋𝗂𝗌𝖾]
Go:
𝗂𝗆𝗉𝗈𝗋𝗍 _ "𝗀𝗈.𝖽𝖻𝗈𝗌.𝖽𝖾𝗏/𝖽𝖻𝗈𝗌-𝖾𝗇𝗍𝖾𝗋𝗉𝗋𝗂𝗌𝖾-𝗀𝗈"
We'll be rolling out the same change for Java soon.
1
2
7
432
Full release notes:
TypeScript: github.com/dbos-inc/dbos-tra…
Python: github.com/dbos-inc/dbos-tra…
Go: github.com/dbos-inc/dbos-tra…
2
116
AI is pushing us to rethink how we build applications. Here's a new blog post from Mike Stonebraker. He argues that applications should move toward durable workflows as AI agents become more common and complex.
A lot of developers are still stitching together stateless services, queues, databases, and state machines to keep things running. That was already painful for traditional applications. Now it's even worse for AI agents that execute long-running tasks, call external tools, and perform actions with side effects.
Mike's argument is that durable workflows should be the default, and you should use your database as the orchestrator.
4
3
20
1,078
Join us for the next DBOS User Group Meetup on October 22!
This month, @Credix_finance and Cortex will share how they're using DBOS to build durable workflows for commercial lending and AI software factories. We'll also share the results of our roadmap survey and open the floor for discussion.
As always, there will be plenty of time to connect with fellow DBOS users and our engineering team. We'd love to hear your feedback and ideas!
Register here: luma.com/2f5n3nr1?tk=GZ8SFs
1
6
515