Graphile Queue Driver

[alex-holovach]

Added Graphile Worker as an alternative queue driver for @workflow/world-postgres, building on top of the queue driver abstraction introduced in #332 .

Usage

Automatic selection via env var

WORKFLOW_QUEUE_DRIVER=graphile

Or explicit factory

import { createGraphileWorkerHttpProxyQueue } from '@workflow/world-postgres';

const world = createWorld({
  queueFactory: createGraphileWorkerHttpProxyQueue,
});

[changeset-bot]

🦋 Changeset detected

Latest commit: 3875887

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 16 packages

Name	Type
@workflow/utils	Patch
@workflow/world-postgres	Patch
@workflow/sveltekit	Patch
@workflow/builders	Patch
@workflow/core	Patch
@workflow/errors	Patch
@workflow/world-local	Patch
workflow	Patch
@workflow/cli	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/web-shared	Patch
@workflow/world-vercel	Patch
@workflow/ai	Patch
@workflow/world-testing	Patch
@workflow/nuxt	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

@alex-holovach is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[alex-holovach]

Create PR Comment job fails with error:

@pranaygp Is it missing some permissions?

[pranaygp]

I'm actively making improvements to the benchmarking stuff so expect some merge conflicts on adding your own stuff to benchmark

[pranaygp]

I don't think we're going to "queue driver" approach (see #332 (comment)) - it defeats the point of the world abstraction

if graphile is a good replacement for pgboss and is faster, then I'm down to just swap out the pg boss implementation in postgres world to use graphile. I added new benchmarks too, so if you redo the PR against the latest main and just swap out the implementation to use graphile without changing the benchmark code, I can trigger the CI testing and benchmarking for you

[alex-holovach]

Agreed, exposing the queue driver adds complexity without clear value for users in this case. I was exploring this to see if we could get lower latency for the Postgres world. Let's see how #332 lands, and I'll revisit this based on that direction.