Peter Kraft
@petereliaskraft.net
Co-founder @ http://dbos.dev • Stanford PhD • Database Geek • Building https://github.com/dbos-inc/dbos-transact-py
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.
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.
March 11, 2025 at 7:19 PM
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.
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.
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?
Would love feedback on it! What works and what isn’t clear?
February 19, 2025 at 4:53 PM
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?
Would love feedback on it! What works and what isn’t clear?
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.
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.
February 7, 2025 at 6:19 PM
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.
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.