Contrast with procrastinate + migrations

[mahmoud]

Hey there! Great project here, big fan of this architecture.

When comparing Python Postgres queues, there's one project conspicuously absent from the Alternatives list, procrastinate: https://github.com/procrastinate-org/procrastinate

That said, I think bq compares favorably. Sure, procrastinate is more mature and may have more features, but it also focuses more on Django and less on SQLAlchemy, and has a much more murky migration story. If I'm understanding correctly, bq should "just work" with Alembic, especially if one creates their own Task models.

So in short:

1. Great work
2. Maybe add Procrastinate to the list of Alternatives
3. Consider adding a short discussion of migrations for when a bq upgrade might change its internal model definitions.

Thanks!

[fangpenlin]

Hey @mahmoud, thanks for the kind words. 😄

I didn't know existence of procrastinate, thanks for brining it up. I've already added it into the alternative list. And yes, I designed this tool to only rely on SQLAlchemy and couple loosely with the data model. So it doesn't care much about the your data model (tables), and you can define your table in whatever shape you want, as long as it's duck-typed correctly for bq to work with. So yes, migration can be done easily with Alembic or any other SQLAlchemy migration tools.

As for migration in readme, yeah, I will add that later.