Repository files navigation

asyncfunctionreadme(){constPgBoss=require('pg-boss');constboss=newPgBoss('postgres://user:pass@host/database');boss.on('error',error=>console.error(error));awaitboss.start();constqueue='some-queue';letjobId=awaitboss.send(queue,{param1:'foo'})console.log(`created job in queue${queue}:${jobId}`);awaitboss.work(queue,someAsyncJobHandler);}asyncfunctionsomeAsyncJobHandler(job){console.log(`job${job.id} received with data:`);console.log(JSON.stringify(job.data));awaitdoSomethingAsyncWithThis(job.data);}

pg-boss is a job queue built in Node.js on top of PostgreSQL in order to provide background processing and reliable asynchronous execution to Node.js applications.

pg-boss relies onSKIP LOCKED, a feature added to postgres specifically for message queues, in order to resolve record locking challenges inherent with relational databases. This brings the safety of guaranteed atomic commits of a relational database to your asynchronous job processing.

This will likely cater the most to teams already familiar with the simplicity of relational database semantics and operations (SQL, querying, and backups). It will be especially useful to those already relying on PostgreSQL that want to limit how many systems are required to monitor and support in their architecture.

• Exactly-once job delivery
• Backpressure-compatible polling workers
• Cron scheduling
• Pub/sub API for fan-out queue relationships
• Deferral, retries (with exponential backoff), rate limiting, debouncing
• Completion jobs for orchestrations/sagas
• Direct table access for bulk loads via COPY or INSERT
• Multi-master compatible (for example, in a Kubernetes ReplicaSet)
• Automatic creation and migration of storage tables
• Automatic maintenance operations to manage table growth

• Node 14 or higher
• PostgreSQL 9.5 or higher

# npmnpm install pg-boss# yarnyarn add pg-boss

• Docs

To setup a development environment for this library:

git clone https://github.com/timgit/pg-boss.gitnpm install

To run the test suite you will need to pgboss access to an empty postgres database. You can set one up using the following commands on a local postgres instance:

CREATEDATABASEpgboss;CREATEuserpostgres WITH PASSWORD'postgres';GRANT ALL PRIVILEGESON DATABASE pgboss to postgres;-- run the following command in the context of the pgboss databaseCREATE EXTENSION pgcrypto;

If you use a different database name, username or password, or want to run the test suite against a database that is running on a remote machine then you will need to edit thetest/config.json file with the appropriate connection values.

You can then run the linter and test suite using

npmtest