3 ms·

Chiming in as the founder of https://www.inngest.com https://www.inngest.com. It looks like Hatchet is trying to catch up with us, though some immediate differ

by tonyhb 2y ago

Chiming in as the founder of https://www.inngest.com 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 our UI * Out of the box support for TS, Python, Golang, Java. We're also interchangeable with zero-downtime language and cloud migrations * I don't know Hatchet's local dev story, but it's a one-liner for us * Batching, to turn eg. 100 events into a single execution * Concurrency, throttling, rate limiting, and debouncing, built in and operate at a function level * Support for your own multi-tenancy keys, allowing you to create queues and set concurrency limits for your own concurrency * Works serverless, servers, or anywhere * And, specifically, it's all procedural and doesn't have to be a DAG. We've also invested heavily in flow control — the aspects of batching, concurrency, custom multi-tenancy controls, etc. are all things that you have to layer over other systems. I expect because we've been around for a couple of years that newer folks like Hatchet end up trying to replicate some of what we've done, though building this takes quite some time. Either way, happy to see our API and approach start to spread :)

BiteCode_dev 2y ago
But we can't self host, right? So it's locked in.
- tonyhb 2y ago
  We're source available, and a helm chart will be coming soon. We're actually doing the last of any queue migrations now. One of our key aspects is reliability. We were apprehensive of officially supporting self hosting with awkward queue and state store migrations until you could "Set it and forget it". Otherwise, you're almost certainly going to be many versions behind with a very tedious upgrade path. So, if you're a cowboy, totally self hostable. If you're not (which makes sense — you're using durable execution), check back in a short amount of time :)
abelanger 2y ago
If 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 a TS [2], Python [3] and Golang SDK [4], has support for throttling and rate limiting [5], concurrency with custom multi-tenancy keys [6], works on serverless [7], and supports procedural workflows [8]. That said, there are certainly lots of things to work on. Batching and better tracing are on our roadmap. And while we don’t have a Java SDK, we do have a Github discussion for future SDKs that you can vote on here: https://github.com/hatchet-dev/hatchet/discussions/436 https://github.com/hatchet-dev/hatchet/discussions/436. [1] https://docs.hatchet.run/home/features/triggering-runs/event-trigger https://docs.hatchet.run/home/features/triggering-runs/event... [2] https://docs.hatchet.run/sdks/typescript-sdk https://docs.hatchet.run/sdks/typescript-sdk [3] https://docs.hatchet.run/sdks/python-sdk https://docs.hatchet.run/sdks/python-sdk [4] https://docs.hatchet.run/sdks/go-sdk https://docs.hatchet.run/sdks/go-sdk [5] https://docs.hatchet.run/home/features/rate-limits https://docs.hatchet.run/home/features/rate-limits [6] https://docs.hatchet.run/home/features/concurrency/round-robin#how-to-use-group_round_robin https://docs.hatchet.run/home/features/concurrency/round-rob... [7] https://docs.hatchet.run/home/features/webhooks https://docs.hatchet.run/home/features/webhooks [8] https://docs.hatchet.run/home/features/child-workflows https://docs.hatchet.run/home/features/child-workflows
p10jkle 2y ago
Maybe let them have their launch? Mitchell said it best: https://x.com/mitchellh/status/1759626842817069290?s=46&t=57h-biZQp-Dcp0k83SJHlg https://x.com/mitchellh/status/1759626842817069290?s=46&t=57...
- tonyhb 2y ago
  Ah, yes, fair. Someone (and I don't know who) mentioned our company so I did jump in... kind of fair, too. I'l leave this thread :)
- cyral 2y ago
  I specifically asked about Inngest, so their comment is very helpful (more so than those only focused on the open source or licensing issue)
cyral 2y ago
Thank you, if you build a .NET API we will give it a try.

by tonyhb 2y ago

BiteCode_dev 2y ago

But we can't self host, right? So it's locked in.

tonyhb 2y ago
We're source available, and a helm chart will be coming soon. We're actually doing the last of any queue migrations now. One of our key aspects is reliability. We were apprehensive of officially supporting self hosting with awkward queue and state store migrations until you could "Set it and forget it". Otherwise, you're almost certainly going to be many versions behind with a very tedious upgrade path. So, if you're a cowboy, totally self hostable. If you're not (which makes sense — you're using durable execution), check back in a short amount of time :)

abelanger 2y ago

If 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 a TS [2], Python [3] and Golang SDK [4], has support for throttling and rate limiting [5], concurrency with custom multi-tenancy keys [6], works on serverless [7], and supports procedural workflows [8]. That said, there are certainly lots of things to work on. Batching and better tracing are on our roadmap. And while we don’t have a Java SDK, we do have a Github discussion for future SDKs that you can vote on here: https://github.com/hatchet-dev/hatchet/discussions/436 https://github.com/hatchet-dev/hatchet/discussions/436. [1] https://docs.hatchet.run/home/features/triggering-runs/event-trigger https://docs.hatchet.run/home/features/triggering-runs/event... [2] https://docs.hatchet.run/sdks/typescript-sdk https://docs.hatchet.run/sdks/typescript-sdk [3] https://docs.hatchet.run/sdks/python-sdk https://docs.hatchet.run/sdks/python-sdk [4] https://docs.hatchet.run/sdks/go-sdk https://docs.hatchet.run/sdks/go-sdk [5] https://docs.hatchet.run/home/features/rate-limits https://docs.hatchet.run/home/features/rate-limits [6] https://docs.hatchet.run/home/features/concurrency/round-robin#how-to-use-group_round_robin https://docs.hatchet.run/home/features/concurrency/round-rob... [7] https://docs.hatchet.run/home/features/webhooks https://docs.hatchet.run/home/features/webhooks [8] https://docs.hatchet.run/home/features/child-workflows https://docs.hatchet.run/home/features/child-workflows

p10jkle 2y ago

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

tonyhb 2y ago
Ah, yes, fair. Someone (and I don't know who) mentioned our company so I did jump in... kind of fair, too. I'l leave this thread :)
cyral 2y ago
I specifically asked about Inngest, so their comment is very helpful (more so than those only focused on the open source or licensing issue)

cyral 2y ago

Thank you, if you build a .NET API we will give it a try.