Skip to content

Update background-tasks.md #284

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
benjie merged 1 commit into from
Aug 21, 2021
Merged

Update background-tasks.md #284

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/pages/postgraphile/background-tasks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,14 +60,14 @@ Other important considerations when choosing a task queue would be:

### Graphile Worker

Graphile Worker is a natural fit for a PostGraphile stack due to it's
Graphile Worker is a natural fit for a PostGraphile stack due to its
PostgreSQL-first nature. It is a simple library that runs Node.js code (or any
code Node.js can delegate to) when a task is queued within the database. Thanks
to PostgreSQL's `LISTEN/NOTIFY` pubsub features, Graphile Worker is notified
when a task is queued and can fetch, execute, and complete a trivial task in
2-3ms from when it was queued; this results in your system feeling very snappy.

Graphile Worker stores tasks into it's own schema within PostgreSQL, and offers
Graphile Worker stores tasks into its own schema within PostgreSQL, and offers
a simple SQL API to create jobs. Queueing a job might look like:

```sql
Expand Down