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...

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/

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...

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...

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?

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. 🧵

I’m joining the DBOS User Group meetup next week to demo our new self-host feature! It’ll be another casual chat on Discord—no recording, just a chance to hang out with the developer team and other users.

You asked, we built. New feature coming soon? 👀

Want to attach a debugger to that weird error you got in production yesterday? With the latest release of the DBOS debugger, you can get pretty close! It lets you take any past trace of a DBOS workflow, execute it locally, and attach a debugger to step through it and see what really happened.

I'm joining the @dbos.dev community meeting tomorrow to chat about our latest engineering progress and roadmap! Come hang out with us—ask us anything about DBOS! This won't be recorded, just a chill session with other developers. www.dbos.dev/dbos-user-gr...

New blog post! Wrote some thoughts on integrating AI agents with real-world systems. I think the missing piece is durable execution (as a library)—the ability to construct reliable tools that interact with external systems and recover smoothly from errors or failures. www.dbos.dev/blog/durable...

I think the single best decision we made when building DBOS was choosing to build everything on Postgres. Why?

Versioning is one of the biggest challenges in software development, especially when an app has long-running workflows that must continue running while the code is upgraded. Interestingly, co-designing durable execution with the runtime can make versioning significantly easier.

Just put together this new demo–an app that visualizes the execution of a durable workflow, showing you what code executes in its backend and how it seamlessly recovers from failures. Would love feedback on it! What works and what isn’t clear?

It’s hard to build a @nextjs.org js app that reliably handles tasks running longer than HTTP request timeouts. Traditional approaches? It's flaky at best. DBOS’s open-source TypeScript library lets you execute durable, long-running tasks directly in your Next.js app. **🧵**

You can't fix what you can't measure. I like this paper's detailed measurement of RPCs in production. A recurring theme in this paper is variation. At hyperscale, RPCs exhibit significant diversity in processing time, CPU/memory usage, and request sizes. dl.acm.org/doi/pdf/10.1... Thoughts in 🧵

Over the past two days, the DBOS team gathered to plan our roadmap for the coming months. We combined creativity with practicality, exploring innovative new features while remaining fully committed to enhancing the user experience, aiming to make building reliable apps effortless.

Store Everything In Postgres An idea on how to radically improve reliability and reduce complexity for stateful apps. www.dbos.dev/blog/what-is...

A good read on how DynamoDB has evolved over the past decade. DynamoDB was originally launched in 2012, and this retrospective paper was published in 2022. www.usenix.org/conference/a... Some takeaways after reading it 🧵

What are your favorite observability frameworks and visualization tools? We're expanding observability support in @dbos.dev to improve custom trace exporting and visualization. We're looking to potentially integrate with some popular tools.

I think the most underrated benefit of durable execution is observability. Durable workflows and steps map 1-to-1 to traces and spans used in OTel and most modern observability frameworks. This makes monitoring easier: how often workflows run, where they spend time, and when they error.

One small ask for the community as we try to make DBOS easier to adopt: We just refreshed the “Learn DBOS” guides in our documentation. I’d be really grateful if anyone could look at the new guides, try them out, and give feedback on what works and what needs to be explained better. Thanks a lot!

Had our first @southbaysystems.xyz coffee chat today in downtown Sunnyvale (forgot to take pics)! It was amazing to meet everyone and chat about anything databases and distributed systems. We’re planning our talk series! If you have a venue or want to present your cool projects, please reach out☀️

Read the "BIG DEAL" CIDR'24 paper by Pat Helland. A Snapshot Isolation semantic contract between the database and applications is the BIG DEAL for making OLTP scalable. I really like the core idea of co-optimizing the database and applications. 🔗 www.cidrdb.org/cidr2024/pap...

Had a wonderful time presenting DBOS to the Bay Area Python Interest Group last night! There was a great discussion about how to integrate durable execution into existing apps--what got people excited about DBOS is that it's just a Python library, so you can "pip install" it into any existing app.

Hello! We are organizing our first South Bay Systems Coffee Chat next week. Register here: lu.ma/2f8y3fsj (w/ @alexmillerdb.bsky.social @yingjunwu.bsky.social) We're planning some talks in the upcoming weeks. Please follow the official account @southbaysystems.xyz 🦋 Stay tuned 👀

The SQLite VLDB'22 paper provides a detailed overview of SQLite architecture. I appreciate the authors' effort in analyzing the performance comparison with DuckDB. They honestly reported OLAP use cases where DuckDB is significantly faster and measured one level deeper. www.vldb.org/pvldb/vol15/...

The DBOS project, which builds a durable workflow execution engine on top of standard Postgres, seems like a really helpful project for folks that don't want to go all-in on using an external service like Temporal, Cadence, etc. supabase.com/blog/durable...

Excited to announce the release of DBOS TypeScript v2.0! With this release, you can easily add durable execution to any TypeScript app, such as apps built with Next.js or Express. 🔗 github.com/dbos-inc/dbo... DBOS enables reliable workflows, cron jobs, and queues -- all built on top of Postgres.

Demo from a user 💙 Jacopo Tagliabue has built a reliable data lake ingestion app using Bauplan and @dbos.dev, all in <100 lines of Python. It uses Bauplan to implement a write-audit-publish pattern and DBOS to orchestrate the pipeline durably. I love how lightweight it is. github.com/BauplanLabs/...

I think serverless is a great fit for agents (as we've been exploring at @dbos.dev). However, AWS Lambda itself is not great for agents, because it's stateless and short-lived. To support long-running agentic workflows, you'll need to stitch Lambdas together via Step Functions and other services.

Great insights! I think stitching together stateless serverless functions for complex workflows is the wrong model. The key is to combine durable execution with serverless platforms to simplify the stack -- that's the vision of @dbos.dev. The new term is micro-monolith :p

Supporting sync & async functions in DBOS decorators was harder than I expected. In frameworks like FastAPI, supporting both is straightforward because it's a simple "fire and forget" dispatch. DBOS Transact is more complex because it executes database code before & after the decorated function.

Just released DBOS Python 0.16.0, with support for asyncio and coroutines. You can now use DBOS decorators with functions defined with 𝘢𝘴𝘺𝘯𝘤 𝘥𝘦𝘧. Everything works out of the box (shoutout to @devhawk.net 🚀): no new syntax required to support async functions.