Simplify AI agent orchestration with Lakebase Postgres
Databricks and CLA developed an agentic auditing system using Lakebase Postgres to reduce document processing time from hours to minutes while maintaining quality.
The useful question is what changes for users, developers or buyers, and whether the announcement stays industry context or becomes something people can actually use.
Databricks and CliftonLarsonAllen LLP (CLA) built an agentic auditing solution on Databricks to automate document processing, cutting extraction time from hours to minutes without sacrificing accuracy. The system leverages Lakebase Postgres, Databricks Apps, Lakeflow Jobs, MLflow, and Unity Catalog Volumes to handle long-running tasks efficiently. Lakebase separates storage from compute, enabling scalable orchestration while eliminating the need for external infrastructure like queueing or observability tools. This architecture simplifies deployment and reduces operational overhead for high-volume document processing workloads.
The orchestration layer, powered by Lakebase Postgres, coordinates tasks, manages retries, and provides real-time visibility into agent workloads. It uses two Postgres tables—tasks and task_attempts—to track task status, agent assignments, and cost metadata. The system employs Postgres-native patterns to ensure concurrency safety, crash resilience, and rate-limit awareness, avoiding the complexity of external schedulers or message brokers. Workers dequeue tasks with row-level locking and prioritization, while a periodic sweeper recovers stalled tasks automatically.
Throttling is handled through three modes—concurrency cap, token budget, or combined cap—to align with endpoint quotas for requests per second or tokens per minute. Decisions are made at dequeue time within the same transaction, ensuring accuracy across worker restarts and multi-replica deployments. The system avoids in-memory queues or separate coordination layers, relying instead on database-backed state for scalability and reliability. Callback handling is designed to be idempotent, preventing duplicate processing even under retries or network interruptions.
Operators gain real-time visibility through an integrated dashboard within the Databricks App, displaying task status, agent performance, and workload cost. Metrics are filterable by date range, task status, and agent, eliminating the need for external polling or separate metrics platforms. This unified approach streamlines monitoring and reduces the complexity of managing distributed agentic workloads at scale.