Postgres Job Queue System

Description

The Postgres Job Queue System modernizes how dotCMS handles background processing by moving job management and tracking directly into the PostgreSQL database. Instead of relying on in-memory or opaque job handling, all background tasks—such as imports, exports, publishing operations, and scheduled jobs—are stored, queued, and tracked with full persistence and visibility.

By making jobs first-class data in the database, dotCMS delivers a more reliable and observable foundation for long-running and asynchronous operations. Jobs survive application restarts, provide clear status and history, and give administrators and developers the insight they need to monitor progress and troubleshoot issues with confidence.

Benefits

For DevOps & Platform Teams

• Track and manage background jobs directly in PostgreSQL for improved observability and operational insight.

• Increase reliability with database-backed job persistence that survives restarts and failures.

• Simplify troubleshooting with clear job status, history, and error details.

For Developers

• Gain better visibility into background task execution without relying on logs alone.

• Inspect job state, failures, and retries through database queries and admin tooling.

• Build and operate more predictable background processes at scale.

Use Cases

Large-Scale Content Imports
An administrator runs a high-volume content import and monitors progress, status, and errors through the database-backed job queue.

Reliable Scheduled Operations
Background tasks such as scheduled publishing, exports, and index rebuilds are tracked consistently and executed reliably—even across restarts.

Operational Troubleshooting
When a background job fails, teams inspect stored job history and error details in PostgreSQL to quickly diagnose and resolve issues.

Resources

• Publishing Queue Documentation

• Database Configuration Documentation