How to set up cron jobs in pg-boss?

Use the boss.schedule() method with cron expressions as documented. For example, boss.schedule('queue-name', '0 * * * *', { data: {} }) creates an hourly job. Ensure the pg-boss instance is started and the scheduler is active in your application.

pg-boss vs Bull: which is better for Node.js?

pg-boss excels if you're already on PostgreSQL and need transactional consistency, while Bull is Redis-based and may offer faster throughput for high-frequency jobs. Choose based on your existing stack and reliability vs. performance trade-offs.

Can pg-boss handle millions of jobs per day?

Yes, but with careful PostgreSQL tuning. It uses SKIP LOCKED for efficiency, but for massive scales, monitor database performance and consider partitioning or dedicated brokers. The README notes multi-master compatibility for scalability in setups like Kubernetes.

How to monitor jobs in pg-boss?

Install the separate @pg-boss/dashboard package for a web interface to view queues and jobs, or use direct SQL queries on the PostgreSQL database. The dashboard provides real-time insights but adds deployment complexity.

Is pg-boss good for serverless functions?

It can work, but persistent PostgreSQL connections may clash with cold starts. Use the @pg-boss/proxy package for connection pooling or optimize for serverless environments by managing connections carefully to avoid timeouts.

How to implement retry logic in pg-boss?

Configure automatic retries with exponential backoff via options like retryLimit and retryDelay when calling boss.work() or boss.send(). The README highlights this feature for resilient job processing without manual intervention.

pgBoss — PostgreSQL Job Queue for Node.js

What is pgBoss?

pg-boss is a job queue library built in Node.js on top of PostgreSQL, designed to provide background processing and reliable asynchronous execution for Node.js applications. It leverages PostgreSQL's SKIP LOCKED feature to ensure exactly-once job delivery and atomic commits, minimizing the need for additional message broker infrastructure. It is ideal for teams already using PostgreSQL who want to simplify their architecture by avoiding extra systems.

Target Audience

Node.js developers and teams already using PostgreSQL who need a durable, atomic job queue for background processing without introducing a separate message broker. It is especially suited for those familiar with relational database semantics and operations like SQL, querying, and backups.

Value Proposition

Developers choose pg-boss because it integrates seamlessly with PostgreSQL, leveraging its robust features for reliability and exactly-once delivery, reducing infrastructure complexity. Its unique selling points include transactional job creation within existing database transactions, SQL support for non-Node.js runtimes, and multi-master compatibility for environments like Kubernetes ReplicaSets.

Queueing jobs in Postgres from Node.js like a boss

Use Cases

Best For

Implementing exactly-once job delivery in Node.js applications using PostgreSQL as the backend.
Creating background job processing systems where jobs must be created within existing database transactions for data consistency.
Scheduling recurring jobs with cron expressions in a PostgreSQL-based environment.
Managing queue storage policies for rate limiting, debouncing, and concurrency control in asynchronous workflows.
Building distributed workflows with pub/sub APIs for fan-out queue relationships.
Deploying job queues in multi-master setups, such as Kubernetes ReplicaSets, without additional message brokers.

Not Ideal For

Applications built on NoSQL databases like MongoDB, as pg-boss is tightly coupled to PostgreSQL and doesn't support alternative backends.
High-throughput systems processing millions of jobs per second, where dedicated message brokers like Kafka or RabbitMQ might offer better scalability and lower latency.
Serverless architectures with frequent cold starts, since pg-boss relies on persistent PostgreSQL connections that can conflict with ephemeral runtime environments.
Teams seeking a fully managed, cloud-native queue service without the overhead of database administration and maintenance.

Pros & Cons

Pros

Exactly-once Delivery

Leverages PostgreSQL's SKIP LOCKED feature to ensure jobs are processed reliably without duplicates, providing atomic commits as highlighted in the README for guaranteed execution.

Transactional Job Creation

Allows jobs to be created within existing database transactions, ensuring data consistency with application logic, a key feature for reliable background processing.

Cron Scheduling

Built-in support for cron expressions enables recurring job scheduling without external tools, simplifying periodic tasks in PostgreSQL-based environments.

Advanced Queue Management

Includes priority queues, dead letter queues, and automatic retries with exponential backoff, offering robust job handling for complex workflows.

SQL and Multi-master Support

Provides SQL access for non-Node.js runtimes and works in multi-master setups like Kubernetes, increasing flexibility for polyglot and distributed systems.

Cons

PostgreSQL Lock-in

The library is deeply integrated with PostgreSQL, making it unsuitable for teams using other databases or wanting a vendor-agnostic solution, as admitted in the README's focus on PostgreSQL users.

Potential Performance Bottlenecks

For extremely high-volume job processing, PostgreSQL might not scale as efficiently as dedicated message brokers, leading to latency issues under heavy loads.

Setup and Maintenance Overhead

Requires managing PostgreSQL database versions, separate packages for dashboard and proxy, and adherence to specific Node.js requirements, adding complexity to deployment.

What is pgBoss?

Target Audience

Value Proposition

Use Cases

Best For

Implementing exactly-once job delivery in Node.js applications using PostgreSQL as the backend.
Creating background job processing systems where jobs must be created within existing database transactions for data consistency.
Scheduling recurring jobs with cron expressions in a PostgreSQL-based environment.
Managing queue storage policies for rate limiting, debouncing, and concurrency control in asynchronous workflows.
Building distributed workflows with pub/sub APIs for fan-out queue relationships.
Deploying job queues in multi-master setups, such as Kubernetes ReplicaSets, without additional message brokers.

Not Ideal For

Applications built on NoSQL databases like MongoDB, as pg-boss is tightly coupled to PostgreSQL and doesn't support alternative backends.
High-throughput systems processing millions of jobs per second, where dedicated message brokers like Kafka or RabbitMQ might offer better scalability and lower latency.
Serverless architectures with frequent cold starts, since pg-boss relies on persistent PostgreSQL connections that can conflict with ephemeral runtime environments.
Teams seeking a fully managed, cloud-native queue service without the overhead of database administration and maintenance.

Pros & Cons

Pros

Exactly-once Delivery

Leverages PostgreSQL's SKIP LOCKED feature to ensure jobs are processed reliably without duplicates, providing atomic commits as highlighted in the README for guaranteed execution.

Transactional Job Creation

Allows jobs to be created within existing database transactions, ensuring data consistency with application logic, a key feature for reliable background processing.

Cron Scheduling

Built-in support for cron expressions enables recurring job scheduling without external tools, simplifying periodic tasks in PostgreSQL-based environments.

Advanced Queue Management

Includes priority queues, dead letter queues, and automatic retries with exponential backoff, offering robust job handling for complex workflows.

SQL and Multi-master Support

Provides SQL access for non-Node.js runtimes and works in multi-master setups like Kubernetes, increasing flexibility for polyglot and distributed systems.

Cons

PostgreSQL Lock-in

The library is deeply integrated with PostgreSQL, making it unsuitable for teams using other databases or wanting a vendor-agnostic solution, as admitted in the README's focus on PostgreSQL users.

Potential Performance Bottlenecks

For extremely high-volume job processing, PostgreSQL might not scale as efficiently as dedicated message brokers, leading to latency issues under heavy loads.

Setup and Maintenance Overhead

Requires managing PostgreSQL database versions, separate packages for dashboard and proxy, and adherence to specific Node.js requirements, adding complexity to deployment.

pgBoss

What is pgBoss?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

pgBoss

What is pgBoss?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?