Inngest is also an easier to use version of Temporal, for serverless.
Currently the major differences are:
- Open source: we're fully open source and self-hostable with Apache 2 license.
- API Integrations: we're building first class support for popular APIs. That makes it really easy to subscribe to webhooks, and when you do API calls you get good retrying behaviour, automatically dealing with rate limits, and a great logging experience. You can write your own integrations and contribute them (that would be awesome), or keep them private to your own codebase.
- React hooks: often background jobs are related to an action a person has done in your app (end-user or an admin tool). We have hooks so you can very easily show the live status of a run exactly how you want.
We released our TS SDK a year ago so had quite a head start in this area. The approach in their V2 release makes them more similar to us, though there are still some large differences, including the fundamental architecture, queueing technology, scale, etc. Some differences you'll notice as a developer:
This is a pretty big point, as you often don't want to run functions sequentially. We're also fully event-driven, allowing you to pause workflows and automatically resume when specific events are received (https://www.inngest.com/docs/reference/functions/step-wait-f...).
We also handle a lot of complexity for you that you'd have to build yourself:
- Rate limiting
- Batching, allowing one function to run from eg. 100 events, instead of 1:1 matching of event->function
- Streaming, for long-running responses
- Auto-cancellation, based off of matching events
- Branch deploys for all workflows, regardless of platform
- Debounce
- And a bunch more such as middleware, error handlers, multi-language support (including zero-downtime live-migrations of long running workflows), fully-offline local development, etc.
In general, I think we're tackling a similar problem with fundamentally different approaches in events and architecture. Trigger definitely have more in the space of integrations, while our approach is: send us anything, no matter the event or source, and we'll work with it.
While I don't know the Trigger folks I'm assuming they've seen similar problems as us and it's fun to tackle this area, so I'm looking forward to seeing how they build out their platform in the future and this area evolves :)
Just want to say, as a somewhat new HN user (l would end up here occasionally via search or Reddit, which I jumped ship after the API changes so HN is my home now), it’s really great to see you and the founder (iirc) of windmill both here in the comments.
We have a growing number of requests for this use-case, but we try to focus on billing right now. However, I can promote Formance (https://www.formance.com/) here that can help on this vertical. They are YC folks, and tackle the use-case of collecting fees and splitting payments. And it's also open source! Hope this helps
What would be the use case for you and the reasons to leave Stripe Connect? We're working with one company to replace their Stripe Connect stack, but it really depends on the specifics of the use case.
My email if useful: anhtho[at]getlago.com
payfac flexibility (aka, no vendor lock-in) — requires an independent platform ledger (where payments have two legs: payee to platform and platform to merchant). Refunds and chargebacks may affect both legs :)
We might have ideas for you! Lago won't cover all these use cases today, but we're working with other players that can provide an alternative stack.
If you're interested, would you mind emailing us? Founders[at]getlago.com
Thanks!
My take (as a paying subscriber to both, largely because I want to support this world and think both teams are insanely talented and great) is that they're solving similar problems, with some different features.
I wish I could use both with a sync between them until I figure out which one I'd want to stick with. Or stick with both.
Having the same debate - feels like this supports a better variety of sources, but Matter has a better/simpler UI for web articles & newsletters specifically.
This is my question. I've hired Matter as my Read It Later app, and it works great. They do seem to be putting some of their premium features behind a paywall, which is annoying, but I'm relatively happy with the app.
