Top all-time · #7649
Hatchet Documentation
Company blog · docs.hatchet.run/blogprogrammingsystems
Hatchet Documentation is the company blog at docs.hatchet.run, writing about programming and systems. Since 2024, 10 different Hacker News readers have linked it 52 times, most often “The Problems with Celery for Python”. It is still writing: the last post was on 2026-08-17, and you can follow it by feed.
Too few sampled comments (9) to say how often HN recommends it.?
Why HN links it
HN commenters link Hatchet's docs pages for features such as streaming task progress, conditional workflows and installation, and a blog post on problems with Celery. Comments cite these as references rather than judge the writing.
Summarised by Claude from a sample of 9 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Hatchet is a developer platform that helps engineering teams build and deploy mission-critical AI agents, durable workflows, and background tasks.
Most-linked posts?
- The Problems with Celery for Python5 people · 5 mentions · first linked 2024-06-05
- Migrating Off of Prisma2 people · 3 mentions · first linked 2024-11-12
- /home/features/streaming2 people · 2 mentions · first linked 2024-03-08
- Use Postgres for your events table2 people · 2 mentions · first linked 2024-11-20
What Hacker News says?
This isn't built specifically for generative AI, but generative AI apps typically have architectural issues that are solved by a good queueing system and worker pool. This is particularly true once you start integrating smaller, self-hosted LLMs or other types of models into your pipeline. > How do you distribute inference across workers? In Hatchet, "run inference" would be a task. By default, tasks get randomly as…
Comment linking /home/features/concurrency/round-robin
on “Show HN: Hatchet – Open-source distributed task queue”Submitted Go is a good fit for agents as a story · 236 points
HN discussionYou can execute a new workflow programmatically, for example see [1]. So people have triggered, for example, 50 child workflows from a parent step. As you've identified the difficult part there is the "collect" or "gathering" step, we've had people hack around that by waiting for all the steps from a second workflow (and falling back to the list events method to get status), but this isn't an approach I'd recommend…
Comment linking /sdks/typescript-sdk/api/admin-client
on “Show HN: Hatchet – Open-source distributed task queue”Submitted Multi-tenant queues in Postgres as a story · 233 points
HN discussionI like that idea, basically the first HTTP request ensures the worker gets spun up on a lambda, and the task gets picked up on the next poll when the worker is running. We already have the underlying push model for our streaming feature: https://docs.hatchet.run/home/features/streaming . Can configure this to post to an HTTP endpoint pretty easily. The daemon feels fragile to me, why not just shut down the worker cl…
Comment linking /home/features/streaming
on “Show HN: Hatchet – Open-source distributed task queue”Submitted The fastest Postgres inserts as a story · 59 points
HN discussionIt's very similar - I used Temporal at a previous company to run a couple million workflows per month. The gRPC networking with workers is the most similar component, I especially liked that I only had to worry about an http2 connection with mTLS instead of a different broker protocol. Temporal is a powerful system but we were getting to the point where it took a full-time engineer to build an observability layer ar…
Comment linking /home/features/durable-execution
on “Show HN: Hatchet – Open-source distributed task queue”Submitted The Problems with Celery for Python as a story · 8 points
HN discussionI need task queues where the client (web browser) can listen to the progress of the task through completion. I love the simplicity & approachability of Deno queues for example, but I’d need to roll my own way to subscribe to task status from the client. Wondering if perhaps the Postgres underpinnings here would make that possible. EDIT: seems so! https://docs.hatchet.run/home/features/streaming
Comment linking /home/features/streaming
on “Show HN: Hatchet – Open-source distributed task queue”Submitted Use Postgres for your events table as a story · 6 points
HN discussionThis should be fixed now, here's the direct link: https://docs.hatchet.run/self-hosting .
Comment linking /self-hosting
on “Show HN: Hatchet – Open-source distributed task queue”Submitted Show HN: Open-source, developer-first prompt engineering platform as a story · 6 points
HN discussionI think we might have had a dead link in the README to our self-hosting guide, here it is: https://docs.hatchet.run/self-hosting . The component which needs the highest uptime is our ingestion service [1]. This ingests events from the Hatchet SDKs and is responsible for writing the workflow execution path, and then sends messages downstream to our other engine components. This is a horizontally scalable service and…
Comment linking /self-hosting/configuration-options
on “Show HN: Hatchet – Open-source distributed task queue”Submitted Migrating Off of Prisma as a story · 4 points
HN discussionEach task in Hatchet is backed by a workflow [1]. Workflows are predefined steps which are persisted in PostgreSQL. If a worker dies or crashes midway through (stops heartbeating to the engine), we reassign tasks (assuming they have retries left). We also track timeouts in the database, which means if we miss a timeout, we simply retry after some amount of time. Like I mentioned in the post, we avoid some classes of…
Comment linking /home/basics/workflows
on “Show HN: Hatchet – Open-source distributed task queue”Submitted Why you need to move beyond Celery in 2024 as a story · 4 points
HN discussionIn https://docs.hatchet.run/home/quickstart/installation , it says > Welcome to Hatchet! This guide walks you through getting set up on Hatchet Cloud. If you'd like to self-host Hatchet, please see the self-hosted quickstart instead. but the link to "self-hosted quickstart" links back to the same page
Comment linking /home/quickstart/installation
on “Show HN: Hatchet – Open-source distributed task queue”Submitted Use Postgres for your events table as a story · 3 points
HN discussion> The Many Problems with Celery: — https://steve.dignam.xyz/2023/05/20/many-problems-with-celer... > The problems with (Python’s) Celery: — https://docs.hatchet.run/blog/problems-with-celery > Dramatiq motivation: — https://dramatiq.io/motivation.html Here are some alternatives: Dramatiq: https://github.com/Bogdanp/dramatiq RQ: https://github.com/rq/rq Huey: https://github.com/coleifer/huey Hatchet: https://github.c…
Comment linking /blog/problems-with-celery
on “Django: what’s new in 6.0”Submitted Migrating to sqlc and pgx for better performance as a story · 3 points
HN discussionI've been referring to this post about issues with Celery: https://docs.hatchet.run/blog/problems-with-celery Does PgQueuer address any of them?
Comment linking /blog/problems-with-celery
on “Show HN: PgQueuer – Transform PostgreSQL into a Job Queue”Submitted Don't Use Celery as a story · 2 points
HN discussionYep, 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 our built-in alerting features which integrate with email and Slack, or configure your own on failure step ( https://docs.hatchet.run/home/features/on-failure-step ). Configurable retry delays are currently in development.
Comment linking /home/features/on-failure-step
on “Launch HN: Hatchet (YC W24) – Open-source task queue, now with a cloud version”Submitted Automating multi-language SDK doc generation with testable code snippets as a story · 1 points
HN discussionIf we’re going to give credit where credit’s due, the history of durable execution traces back to the ideas of AWS step functions and Azure durable functions alongside the original Cadence and Conductor project. A lot of the features here are attempting to make patterns in those projects accessible to a wider range of developers. Hatchet is also event driven [1], has built-in support for tracing and metrics, and has…
Comment linking /home/features/child-workflows
on “Launch HN: Hatchet (YC W24) – Open-source task queue, now with a cloud version”Hi Gabe, also Gabe here. Yes, this is a core usecase we're continuing to develop. Prior to Hatchet I spent some time as a contractor building LLM agents where I was frustrated with the state-of-tooling for orchestration and lock in of some of these platforms. To that end, we’re building Hatchet to orchestrate agents with features that are common like streaming from running workers to frontend [1] and rate limiting […
Comment linking /home/features/rate-limits
on “Launch HN: Hatchet (YC W24) – Open-source task queue, now with a cloud version”I'm saying there are too many things to learn to get even a simple example let alone a real world example going. Have a look at their examples at https://docs.hatchet.run/home/conditional-workflows
Comment linking /home/conditional-workflows
on “Show HN: Hatchet v1 – A task orchestration platform built on Postgres”Thanks for this feedback, we'll add some details and an architecture diagram. The simplest way to run hatchet is with `hatchet-lite`[0] which bundles all internal services. For most deployments we recommend running these components separately hence the multiple services in the helm chart [1]. RabbitMQ is now an optional dependency which is used for internal-service messages for higher throughput deployments [2]. You…
Comment linking /self-hosting/improving-performance
on “Show HN: Hatchet v1 – A task orchestration platform built on Postgres”Quick feedback: Would love to see some sort of architecture overview in the docs The top-level docs have a section on "Deploying workers" but I think there are more components than that? It's cool there's a Helm chart but the docs don't really say what resources it would deploy https://docs.hatchet.run/self-hosting/docker-compose ...shows four different Hatchet services plus, unexpectedly, both a Postgres server and…
Comment linking /self-hosting/docker-compose
on “Show HN: Hatchet v1 – A task orchestration platform built on Postgres”Hey there - all of our self-hosting docs show you how to set up Postgres: https://docs.hatchet.run/self-hosting Would love to hear more about what you found confusing!
Comment linking /self-hosting
on “Show HN: Hatchet v1 – A task orchestration platform built on Postgres”
