Our next South Bay Systems meetup will be on March 31. We've got two awesome deep-dive talks from Sugu Sougoumarane (Consensus and Multigres) and @stuhood.sh (Full-Text Search and ParadeDB).
Food and beverages will be provided, courtesy of our host, Snowflake. Register here: luma.com/2g3exvjw
Applications already depend on a database (usually Postgres). So why not use the database itself as the bridge between languages?
We just published a new blog post on how we tackled language interoperability without adding another layer of infrastructure.
www.dbos.dev/blog/making-...
Creating agent workflows and architecting the logic is one thing, making them durable and fail-safe is another👇
New integration for durable agent workflows with @dbos.dev execution - Make sure your agents survive crashes, restarts, and errors without writing any checkpoint code.
We're starting a new series highlighting the features and integrations our team has been shipping each
month.
We shipped Kotlin support, workflow patching & lineage tracking, dynamic cron, configurable alerting, a new MCP server, and more.
Read the full update here:
www.dbos.dev/blog/dbos-ne...
People used to complain that the DBOS UI wasn't available locally. Good news: it is now, and it's free for open-source local dev.
Run a local DBOS UI right on your laptop and actually see your workflows while you build. Debugging hits different when it's visual.
docs.dbos.dev/production/s...
Want to hear what two database professors Mike Stonebraker and @andypavlo.bsky.social really think about AI and data systems, plus a recap of 2025 and predictions for 2026? In case you missed the webinar, watch the full recording here: www.youtube.com/watch?v=RnQK...
A screenshot of using Logfire + DBOS + Pydantic AI agent.
I wrote a tutorial on integrating DBOS with Logfire. It's super easy to set up (kudos to the @pydantic.dev team!) -> just a few lines to configure the exporter and your Logfire write token. Once it's running, you'll get a unified view of your app with logs + traces in one place.
Screenshot of https://github.com/dbos-inc
I care more about helping developers build reliable systems than chasing vanity metrics such as GitHub stars. Still, seeing the DBOS Python repo reach 1K 🌟 makes me smile.
Thanks for building durable workflows with @dbos.dev. Full speed ahead - Java release coming soon!
A screenshot of how DBOS only has 6 dependencies: https://www.npmjs.com/package/@dbos-inc/dbos-sdk
Just released DBOS TypeScript v4.0!
Following our Python release, we trimmed dependencies in TS too: down from 27 to 6, while still implementing durable workflows and queues in a single library.
It works with both TS/JS and requires no extra orchestrator.
Release notes: github.com/dbos-inc/dbo...
At some point I might write a blog post on "How to add DBOS to any AI framework". AI agents are basically loops, and DBOS makes loops durable with a few decorators.
Last week, I showed DBOS + Pydantic AI. Today, I implemented DBOS + CrewAI within a few hours. PR: github.com/crewAIInc/cr...
The intro video for my talk at #p99conf 💙
Nothing makes me happier than seeing our customers win.
If you spend time on GitHub, you've probably spotted the Dosu bot all over, including in some of the most popular AI frameworks. Now it's even more reliable: their ingestion and RAG pipelines run on @dbos.dev
Blog: dosu.dev/blog/migrate...
Screenshot of https://www.reddit.com/r/dbos/
DBOS now has its own subreddit! Come hang out, share ideas, ask questions, and help us shape the future of durable workflows and queues.
Fun fact: our CEO @jedberg.bsky.social (aka jedberg) was the first employee at Reddit, and now he's our mod. Full circle moment.
🔗 www.reddit.com/r/dbos/
A user promoting DBOS user group on Twitter
The highlight of every user group is hearing directly from our users.
Join us to see how doohickey.ai uses @dbos.dev to automate AI-powered ERP integrations.
Thursday, August 28 @ 11AM PT
Zoom (no recording — so don’t miss it!)
lu.ma/8rqv5o5z
☕️ Friends in the Bay Area: August coffee chat time!
We're hosting the @southbaysystems.xyz August Coffee Chat next week. Come hang out with other systems folks for some casual conversations.
🗓 Thursday, August 28, 5–6 pm
📍 Courtyard outside Philz Sunnyvale
🔗 lu.ma/97e10ef4
Hope to see you there!
A new episode of SE Radio is live! I had a great time chatting with host Kanchan Shringi about what it takes to build durable, observable, and scalable systems, and why that matters for modern applications.
Happy to hear thoughts and feedback!
se-radio.net/2025/08/se-r...
A code snippet for DBOS that uses DBOS.write_stream and DBOS.read_stream to stream results back to the client.
LLM streaming is already common, but I like this newly released durable streams feature. In DBOS, streams are append-only, durable records tied to a workflow.
If a process crashes, the full history is persisted in the database, making it easy to restore context and resume from where it left off.
New Screaming in the Cloud episode! @quinnypig.com and our CEO @jedberg.bsky.social "chat about Jeremy's "build for three" rule, a plan for scale without going crazy, why he set Reddit's servers to Arizona time to dodge daylight saving time, and how DBOS makes your app as tough as your data."
The South Bay Systems meetup is back on July 22!
We're excited to welcome Jacopo Tagliabue (co-founder and CTO of Bauplan) for a talk on Speedrunning the Lakehouse: Shipping a FaaS that Looks Like a Database (and Vice Versa).
🔗 lu.ma/5zcpbae9
Join us for the June DBOS User Group Meetup next week!
We're excited to welcome engineers from Yutori (yutori.com), one of our customers building powerful AI agents that can autonomously perform digital tasks across the web. They'll share how they're using DBOS to make these agents reliable.
☀️Summer is heating up, and so is systems chat!
We're hosting a @southbaysystems.xyz June Coffee Chat next week. Come hang out with other systems folks for some casual conversations.
🗓 Thursday, June 5, 5–6 pm
📍 Courtyard outside Philz Sunnyvale
Register here: lu.ma/67yxr1pn
Hope to see you there!
🍴Wrote a new blog post on how durable workflows simplify bug fixing and recovery. Having persistent records of past executions is helpful because you can "fork" from the last failure point to a new code version, without duplicating already completed work.
www.dbos.dev/blog/handlin...
📣 DBOS User Group meetup next week: you're invited!
We'll walk through our new Python 1.0 release, plus a sneak peek at the eng roadmap for TypeScript, graph visualization, and more languages.
It's a casual chat on Discord, no recording, just hang out with fellow users. Come say hi! lu.ma/8ltwl38e
🚀 DBOS Python 1.0 is here!
A year ago, we launched DBOS with a simple belief: durable workflows should be built into your applications, not bolted on.
Today, we're excited to release DBOS Python 1.0, a major milestone shaped by months of iteration and community input.
⭐ github.com/dbos-inc/dbo...
An illustration for DBOS durable workflow timeouts.
Timeouts are useful for building resilient systems. They help prevent systems from waiting indefinitely and free up resources while maintaining responsiveness under heavy load.
Databases provide timeouts for individual queries, transactions, etc. But you often need end-to-end durable timeouts 🧵
Just released some new DBOS features!
- Auto-cancel on timeout is useful to avoid wasting resources/API calls when workflows can't meet SLAs.
- Workflow fork enables failure recovery (from 3rd party services or bugs) with clean retries.
- DBOS Client is great for programmatic workflow control.
Big DBOS release today! 🚀🚀🚀 Here are some of the new features that just came out:
- Workflow cancel after timeouts
- Workflow "fork" from a step
- Managing workflows from DBOS Client
- Filtering workflows on ID prefixes
Python notes: github.com/dbos-inc/dbo...
TS notes: github.com/dbos-inc/dbo...
Storing everything in database tables makes it easy to query, modify, and debug. You get full visibility and control over queues, workflows, and state — all via SQL. We’re now extending that power with richer visualizations in the web UI. Looking for feedback — what would help you most?
Screenshot of the paper File Systems Unfit as Distributed Storage Backends: Lessons from 10 Years of Ceph Evolution https://dl.acm.org/doi/pdf/10.1145/3341301.3359656
Conventional wisdom says standing on the shoulders of giants—leveraging battle-tested technologies. However, it's worth re-evaluating that decision when prior art becomes a substantial blocker. Sometimes, you need a clean-slate approach. This paper shows a good example: why/how Ceph built BlueStore.
The most common request we've heard from users has been better support for self-hosting DBOS at scale. We're excited to introduce 𝐂𝐨𝐧𝐝𝐮𝐜𝐭𝐨𝐫, a managed service for operating self-hosted apps in production.
What sets DBOS apart is that Conductor runs out of band with no access to your private data. 🧵