back
user profile
abelanger
1,612karma·202submissions·July 2, 2019
about
Co-founder of Hatchet (W24, https://hatchet.run), a task queue built on Postgres. Previously co-founder of Porter (S20, https://porter.run)
recent activity (202 total)
comment
We use gRPC on our workers. All API specs can be found here: https://github.com/hatchet-dev/hatchet/tree/main/api-contrac... However, the SDKs are very tightly int…
comment
Really appreciate the candid feedback, and glad to hear you like the product. We ran a broken links checker against our docs, but it's possible we missed something. Is there anywhere you're …
comment
Re DBOS - yep, this is exactly what the child spawning feature is meant for: https://docs.hatchet.run/home/child-spawning The core idea being that you write the "parent"…
comment
Yeah, part of this rewrite was separating our monitoring tables from all of our queue tables to avoid problems like table bloat. At one point we considered partitioning on the status of a queue item (…
comment
Thanks! There are SDKs for Python, Typescript and Go. We've gotten a lot of requests for other SDKs which we're tracking here: https://github.com/hatchet-dev/hatchet…
comment
I'm not sure of the exact threshold, but the pathological case seemed to be (1) many tasks in the backlog, (2) many workers, (3) workers long-polling the task tables at approximately the same tim…
comment
Yep, durable execution-wise we're targeting a very similar use-case with a very different philosophy on whether the orchestrator (the part of the durable execution engine which invokes tasks) sho…
comment
You can get around some of this coordination by doing more work locally, in-process -- but you're risking the availability of your primary API. The work that you're doing as a background job…
comment
Definitely agree that the dev experience is better with a library, particularly for lightweight and low-volume tasks (Hatchet is also moving in the same direction, we'll be releasing library-only…
comment
Disclaimer: I'm a co-founder of Hatchet ( https://github.com/hatchet-dev/hatchet ), which is a Postgres-backed task queue that supports durable execution. > Because a step …
comment
I've found that I rely most heavily on LLMs when: 1. I'm developing a utility package that's easily testable and I'm certain of the interface. I'll write the interface for the…
comment
It's not clear how many records were generated in the sample dataset for these benchmarks. The methodology [1] and Github repo [2] show how to seed tables of 1k records, but it's not clear w…
comment
Hatchet ( https://hatchet.run ) | New York City (IN-PERSON) | Full-time We're hiring a founding engineer to help us with development on our open-source, distributed task queue: https:&…
comment
Yep, we have support for "retry 5 times, then give up" ( https://docs.hatchet.run/home/features/retries/simple ) and "text me" - you can use either ou…
comment
You're right, if all you need is a queue with a small number of workers connected at low volume, you don't need Hatchet or any other managed queue - you can get some pretty performant behavi…
comment
Thanks! Yes, our recommended approach is to write a parent workflow which calls child workflows registered on a different worker. We have users who are managing a set of Python functions from a Typesc…