Cool project. Every time one of these projects comes up, I'm always somewhat disappointed it isn't an open source / postgres version of GCP Cloud Tasks. All I ever want is a queue where I submit a message and then it hits an HTTP endpoint with that message as POST. It is such a better system than dedicated long running worker listeners, because then you can just scale your HTTP workers as needed. Pairs extremely well…
Show HN: Hatchet v1 – A task orchestration platform built on Postgres
31–40 of 78 posts
Re: Show HN: Hatchet v1 – A task orchestration platform built on Postgres
#32A lot of these tools show off what a full success backlog looks like, in reality I care significantly more about what failure looks like, debugging, etc.
Re: Show HN: Hatchet v1 – A task orchestration platform built on Postgres
#33Re: Show HN: Hatchet v1 – A task orchestration platform built on Postgres
#34Re: Show HN: Hatchet v1 – A task orchestration platform built on Postgres
#35How does this compare to other pg-backed python job runners like Procrastinate [0] or Chancy [1]? [0] https://github.com/procrastinate-org/procrastinate/ [1] https://github.com/TkTech/chancy
Re: Show HN: Hatchet v1 – A task orchestration platform built on Postgres
#36How does this compare to other pg-backed python job runners like Procrastinate [0] or Chancy [1]? [0] https://github.com/procrastinate-org/procrastinate/ [1] https://github.com/TkTech/chancy
Celery also has postgres backend, but I maybe it's not as well integrated.
Re: Show HN: Hatchet v1 – A task orchestration platform built on Postgres
#37This is awesome and I will take a closer look! One question: We ran into issue with using Postgres as a message queue with messages that need to be toasted/have large payloads (50mb+). Only fix we could find was using unlogged tables and a full vacuum on a schedule. We aren’t big Postgres experts but since you are I was wondering if you have fixed this issue/this framework works well for large payloads.
Re: Show HN: Hatchet v1 – A task orchestration platform built on Postgres
#38Cool project. Every time one of these projects comes up, I'm always somewhat disappointed it isn't an open source / postgres version of GCP Cloud Tasks. All I ever want is a queue where I submit a message and then it hits an HTTP endpoint with that message as POST. It is such a better system than dedicated long running worker listeners, because then you can just scale your HTTP workers as needed. Pairs extremely well…
Re: Show HN: Hatchet v1 – A task orchestration platform built on Postgres
#39How does this compare to other pg-backed python job runners like Procrastinate [0] or Chancy [1]? [0] https://github.com/procrastinate-org/procrastinate/ [1] https://github.com/TkTech/chancy
Re: Show HN: Hatchet v1 – A task orchestration platform built on Postgres
#40This is awesome and I will take a closer look! One question: We ran into issue with using Postgres as a message queue with messages that need to be toasted/have large payloads (50mb+). Only fix we could find was using unlogged tables and a full vacuum on a schedule. We aren’t big Postgres experts but since you are I was wondering if you have fixed this issue/this framework works well for large payloads.
Don't put them in the queue. Put the large payload into an object store like s3/gcs and put a reference into the db or queue