From 7161466e3069a8ba39ad1e0f70bed73f42fb0af1 Mon Sep 17 00:00:00 2001 From: Naomi Date: Thu, 19 Aug 2021 23:39:15 -0700 Subject: [PATCH] Update background-tasks.md --- src/pages/postgraphile/background-tasks.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pages/postgraphile/background-tasks.md b/src/pages/postgraphile/background-tasks.md index 28c0ab9ba..ea31ebdea 100644 --- a/src/pages/postgraphile/background-tasks.md +++ b/src/pages/postgraphile/background-tasks.md @@ -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