Integration with apalis

[geofmureithi]

Hey!
I like this lib (and the work done here) and since apalis is pretty agnostic with its sources, would you consider an integration?
Here are possible ways:

1. Separate lib, something like apalis-pgboss-rs
2. Feature gate: pgboss-rs = { version = "*", features="apalis" }
3. Just include an example

Let me know your thoughts

[rustworthy]

Habari!

Just a disclaimer: this is mostly a port of Tim Jones' work. This crate is still work-in-progress.

I am open to integrations sure thing, it's just that I have no real experience with apalis yet. I am guessing what you are suggesting implies implementing Storage? In general, I think starting with an example (option 3 from the issue text) may be useful: this may help evaluate if option (1) or option (2) should be followed later on.

You think you could help with an example?

Cheers,
Pavel

[geofmureithi]

Njema!

Awesome, makes sense. Let me work on an example then we can discuss from there.

Just for clarity, Storage was dropped in v1 in favor of Backend but the idea is the same.

I am curious about your plans with the node.js part. Do you plan to support compatibility with the pg-boss node version? That would be really nice.

[rustworthy]

Sounds great!

So my initial intent was to wait for a major release (was major version 10 of the Node.js package at that point) and start supporting compatibility from there (which implies including migrations similar to this): this is because there were some backward incompatible changes planned at that time and I wanted to weather the storm while also working on the port.
I think I am going to stick to this plan but with regard to the current version of the package. I think I may also re-visit the bits where I added procedures instead of the original prepared statements for better interop.

[geofmureithi]

Awesome, sounds like a solid plan. Let me work on something then get back to you.

[rustworthy]

Hey @geofmureithi!

I now see there have been significant changes in the original package, to the extent that no automatic migration is possible, and folks are advised to install the app into a new schema and then migrate jobs with an sql query or the API that the pgboss package exposes.

I will be adjusting this crate to those changes according this plan

• update ddl and check we are in full sync
• remove procedures that were not there originally (folks may not want to run our migrations)
• adjust the tests

It maybe makes sense to proceed with the integration example after this is merged, wdyt?

P.S.: accumulating the changes in #17

[geofmureithi]

Sure, but I dont think that would affect the example much as apalis would not care how the underlying implementation. On apalis' side, we will care about 3 main things:

1. How to get a Stream of tasks
2. How to push a task
3. How to ACK a task.

I dont think the changes you are anticipating will change these overall APIs that much, hence it should be good IMO.
Let me know if I am getting this all wrong 😅

[rustworthy]

Ok I see, I will do my best to reduce the changes to the crate's API, at least with regard to the methods (on the Client) responsible for fetching, pushing and reporting on the job's state.

[geofmureithi]

Hey yoh!

Any update on this?

[rustworthy]

Hi @geofmureithi , earlier I caught up with the pgboss "upstream", but there has been another DDL change in there since then. I am currently not using pgboss and so cannot keep the bindings in sync as part of my routine. I will probably come back to this at some point. Please let me know what you think or plan.

[geofmureithi]

I am willing to: 1. Support your current implementation 2. Allocate some time to help keep it in sync. I am pretty flexible and can work with you as long as the required guidelines are provided.

…

On Tue, 3 Mar 2026 at 00:02, Pavieł Michalkievič ***@***.***> wrote: *rustworthy* left a comment (rustworthy/pgboss-rs#15) <#15 (comment)> Hi @geofmureithi <https://github.com/geofmureithi> , earlier I caught up with the pgboss "upstream", but there has been another DDL change in there since then. I am currently not using pgboss and so cannot keep the bindings in sync as part of my routine. I will probably come back to this at some point. Please let me know what you think or plan. — Reply to this email directly, view it on GitHub <#15 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWXVRGWXEEA3DDNOI4BGZOD4OXZF5AVCNFSM6AAAAACOEXXVXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSOBWHA4TKMRZGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[rustworthy]

hi @geofmureithi !

I've happily sent an invite for you to co-maintain the crate. As for the guidelines: I think one of them is something you pointed out here - the compatibility with the original application and so ended up double-checking things manually comparing the dumps . I also have a local copy of the original examples so that i can run those against the db migrated from within this crate.

I also tried to keep the bindings as lean as possible, and was planning to add worker feature down the road.

One thing with regard to keeping things in sync, I think there is no need (fortunately) to support a migration until v0.1.0 is published, but once it's there, we will need to add and run something similar to this

[geofmureithi]

I am currently OOO. Will pick this up next week.

…

On Wed, 4 Mar 2026 at 10:08, Pavieł Michalkievič ***@***.***> wrote: *rustworthy* left a comment (rustworthy/pgboss-rs#15) <#15 (comment)> hi @geofmureithi <https://github.com/geofmureithi> ! I've happily sent an invite for you to co-maintain the crate. As for the guidelines: I think one of them is something you pointed out here <#15 (comment)> - the compatibility with the original application and so ended up double-checking things manually comparing the dumps <https://github.com/rustworthy/pgboss-rs/blob/ed8ccb49888bdd5c1fcfe0c196786445fee22f70/Makefile#L46-L100> . I also have a local copy of the original examples <https://github.com/timgit/pg-boss/tree/master/examples> so that i can run those against the db migrated from within *this* crate. I also tried to keep the bindings as lean as possible, and was planning to add worker feature down the road. One thing with regard to keeping things in sync, I think there is no need (fortunately) to support a migration until v0.1.0 is published, but once it's there, we will need to add and run something similar to this <https://github.com/timgit/pg-boss/blob/f77f98c28e4d3622b7dc25a3995733aa5b53f8d8/src/migrationStore.ts#L57> — Reply to this email directly, view it on GitHub <#15 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWXVRGXMTFFOMQATDZE4YI34O7I5NAVCNFSM6AAAAACOEXXVXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSOJVG4YTMNJQGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>