Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Hatchet (YC W24) – Open-source task queue, now with a cloud version

news.ycombinator.com

Post reply on HN
Print view View original

61–70 of 102 posts

Re: Launch HN: Hatchet (YC W24) – Open-source task queue, now with a cloud version

#61

Post by bbor »

numlocked wrote: post #14

Being MIT licensed, does that mean that another company could also offer this as a hosted solution? Did you think about encumbering with a license that allowed commercial use, but prohibited resale? Also, somewhat related, years ago I wrote a very small framework for fan-out of Django-based tasks in Celery. We have been running it in production for years. It doesn't have adoption beyond our company, but I think there…

I feel like just rehosting an actively maintained github repo would draw significant negative PR. And even if not, I feel like part of this business plan revolves around becoming a relatively big part of the ecosystem; one or two cloud providers potentially poaching your customers with a drop down option could easily be worth more in advertising than you’re losing in subscription dollars.

I’m guessing :shrug:

Re: Launch HN: Hatchet (YC W24) – Open-source task queue, now with a cloud version

#63

Post by abelanger »

numlocked wrote: post #14

Being MIT licensed, does that mean that another company could also offer this as a hosted solution? Did you think about encumbering with a license that allowed commercial use, but prohibited resale? Also, somewhat related, years ago I wrote a very small framework for fan-out of Django-based tasks in Celery. We have been running it in production for years. It doesn't have adoption beyond our company, but I think there…

Very cool! Does it support the latest version of Celery?

And to answer the question, no, the license doesn't restrict a company from offering a hosted version of Hatchet. We chose the license that we'd want to see if we were making a decision to adopt Hatchet.

That said, managing and running the cloud version is significantly from a version meant for one org -- the infra surrounding the cloud version manages hundreds and eventually thousands of different tenants. While it's all the same open-source engine + API, there's a lot of work required to distribute the different engine components in a way that's reliable and supports partitioning databases between tenants.

Re: Launch HN: Hatchet (YC W24) – Open-source task queue, now with a cloud version

#64

Post by [deleted] »

bbor wrote: post #61
numlocked wrote: post #14

Being MIT licensed, does that mean that another company could also offer this as a hosted solution? Did you think about encumbering with a license that allowed commercial use, but prohibited resale? Also, somewhat related, years ago I wrote a very small framework for fan-out of Django-based tasks in Celery. We have been running it in production for years. It doesn't have adoption beyond our company, but I think there…

I feel like just rehosting an actively maintained github repo would draw significant negative PR. And even if not, I feel like part of this business plan revolves around becoming a relatively big part of the ecosystem; one or two cloud providers potentially poaching your customers with a drop down option could easily be worth more in advertising than you’re losing in subscription dollars. I’m guessing :shrug:

[deleted]

Re: Launch HN: Hatchet (YC W24) – Open-source task queue, now with a cloud version

#66

Post by barrell »

I’ve been through a whole journey with distributed tasks queues - from celery, to arq, to recently hatchet. Not only is hatchet the only solution that doesn’t make me want to tear my hair out, but the visibility the product gives you is amazing! Being able to visually explore logs, props, refrigerate specific queues etc has been a game changer,

Also, minor thing, but the granularity around rate limiting and queues also feels like quite the luxury. Excited for more here too

Cool to see them on the front page, congrats on the launch

Re: Launch HN: Hatchet (YC W24) – Open-source task queue, now with a cloud version

#67

Post by n00bskoolbus »

This looks really awesome! We were just discussing at work how we're having a hard time finding a framework for a task queue that supports dependant tasks and has support for Python & TS. I suppose writing that out it does feel like a pretty specific requirement. I'm glad to see this pop up though, feels very relevant to me right now.

A question around workflows having just skimmed your docs. Is it possible to define a workflow that has steps in Python and a TS app?

Re: Launch HN: Hatchet (YC W24) – Open-source task queue, now with a cloud version

#68

Post by cyral »

p10jkle wrote: post #48
tonyhb wrote: post #33

Earlier quoted context omitted.

Chiming in as the founder of https://www.inngest.com . It looks like Hatchet is trying to catch up with us, though some immediate differences: * Inngest is fully event driven, with replays, fan-outs, `step.waitForEvent` to automatically pause and resume durable functions when specific events are received, declarative cancellation based off of events, etc. * We have real-time metrics, tracing, etc. out of the box in o…

Maybe let them have their launch? Mitchell said it best: https://x.com/mitchellh/status/1759626842817069290?s=46&t=57...

I specifically asked about Inngest, so their comment is very helpful (more so than those only focused on the open source or licensing issue)

Re: Launch HN: Hatchet (YC W24) – Open-source task queue, now with a cloud version

#69

Post by abelanger »

n00bskoolbus wrote: post #67

This looks really awesome! We were just discussing at work how we're having a hard time finding a framework for a task queue that supports dependant tasks and has support for Python & TS. I suppose writing that out it does feel like a pretty specific requirement. I'm glad to see this pop up though, feels very relevant to me right now. A question around workflows having just skimmed your docs. Is it possible to define…

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 Typescript backend with this approach.

It's also possible to have a single DAG workflow (instead of parent/child) that has steps across multiple languages, but you'll need to use a relatively undocumented method called `RegisterAction` within each SDK and use the API to register the DAG (instead of using the built-in helpers) for this use-case. So we recommend using the parent/child workflows instead.

Re: Launch HN: Hatchet (YC W24) – Open-source task queue, now with a cloud version

#70

Post by cyral »

tonyhb wrote: post #33
cyral wrote: post #23

How does this compare to Temporal or Inngest? I've been investigating them and the durable execution pattern recently and would like to implement one soon.

Chiming in as the founder of https://www.inngest.com . It looks like Hatchet is trying to catch up with us, though some immediate differences: * Inngest is fully event driven, with replays, fan-outs, `step.waitForEvent` to automatically pause and resume durable functions when specific events are received, declarative cancellation based off of events, etc. * We have real-time metrics, tracing, etc. out of the box in o…

Thank you, if you build a .NET API we will give it a try.
Post reply on HN