June 2026 Summaries
4 posts from DBOS
Filter
Month:
Year:
Post Summaries
Back to Blog
DBOS has introduced metrics for durable workflows, enabling users to integrate these into their observability stacks using DBOS Conductor, with compatibility for Prometheus/OpenMetrics endpoints. This allows monitoring of application workflows, steps, and executors in tools like Datadog, Prometheus, and Grafana by scraping metrics through an authenticated GET request with a Conductor API key. Users can monitor various aspects such as workflow throughput, queue health, latency, step outcomes, and executor status, with metrics labeled by application and workflow details for analysis and aggregation. The system supports custom alerting rules using PromQL, allowing alerts based on workflow conditions. Available on DBOS Teams plans, users can access these features with DBOS Python ≥2.23.0 or DBOS TypeScript ≥4.19.0 by generating an API key and configuring their monitoring systems accordingly.
Jun 22, 2026
426 words in the original blog post.
In recent updates, the DBOS product team has enhanced both workflow observability and transactional application development. Key advancements include the introduction of aggregate views and workflow metrics exports in DBOS Conductor, alongside role-based access control and bulk workflow fork operations from the user interface. Additionally, DBOS Transact has been improved with pluggable data sources, enhanced Java and Go feature parity, and the inclusion of SQLite backend support for Go. The platform now offers new integrations with AI frameworks and a plugin for Google ADK, enhancing reliability and scalability for AI applications. Improvements in DBOS Transact also feature latency enhancements for durable streams, bulk send operations, and expanded support for multiple databases, which collectively streamline operations and bolster exactly-once execution for database workflows. DBOS Conductor's updates facilitate easier management and monitoring of workflows through multi-dimensional filtering, aggregate views, and seamless integration with popular observability platforms, while role-based access control ensures secure management across teams.
Jun 18, 2026
1,573 words in the original blog post.
The text explores the benefits of co-locating workflow systems within the same Postgres database as application data, challenging conventional wisdom that these should be separated. It argues that this integration allows for seamless transaction management, enhancing the ability to handle complex distributed system challenges like idempotency and atomicity. By combining workflow metadata and application data in a single database transaction, the text explains how this approach can simplify processes such as avoiding duplicate operations and ensuring atomic updates across systems. It highlights methods like using a transactional workflow outbox to maintain consistency and reliability without the additional operational complexities of separate workflow engines, suggesting that these practices can lead to more scalable and efficient system designs. The piece concludes by inviting readers interested in building robust systems to explore more about Postgres-backed durable workflows through resources provided by DBOS.
Jun 15, 2026
1,048 words in the original blog post.
Scaling Postgres-backed task queues for durable workflows presents challenges, particularly as workloads grow to tens of billions of workflows per month. A major issue is contention between multiple workers attempting to dequeue the same tasks simultaneously, which can be mitigated using Postgres's SKIP LOCKED feature, allowing workers to select and lock only those tasks not already being processed. However, transaction isolation levels, specifically REPEATABLE READ, can cause serialization failures at high concurrency, which can be alleviated by using READ COMMITTED for queues without global flow control. Additionally, inefficient indexes can lead to high CPU usage, necessitating more selective indexing that optimizes query performance and reduces maintenance costs, ultimately allowing the system to scale to over 30,000 workflows per second. These optimizations significantly enhance throughput and efficiency, demonstrating the potential for Postgres-backed systems to handle massive scales with proper tuning and adjustments.
Jun 02, 2026
1,067 words in the original blog post.