Live data from Hacker News

Show HN: Inngest 1.0 – Open-source durable workflows on every platform

inngest.com

41–50 of 55 posts

Re: Show HN: Inngest 1.0 – Open-source durable workflows on every platform

#41
post #21

Earlier quoted context omitted.

> My only issue was that the execution of an inngest function wasn't completely intuitive, at least in TS, and you have to think in terms of inngest or, more precisely, the abstraction it is providing. Is it an actor, a step function, an event consumer, a saga? or a combination of some? I'm personally curious about this. I'm not saying you don't, but why would you need to understand what kind of abstraction it is bey…

Because code doesn't execute as you might think it does, which is why Inngest has docs describing best practices. You have to be careful about how you structure effectful code and how you might share data between steps, and you have to understand when that code might be executed, so the more you know about that, the better. Inngest itself, at least with Vercel, doesn't do its own compute. Inngest, as far as I know, d…

> Inngest, as far as I know, does not do its own compute, it piggybacks on your own, so if you're not careful you can go hard with inngest but you'll see the impact on your hosting bill; especially with Vercel.

Disclaimer: CEO of DBOS here (Ingest competes with some of what we do).

DBOS provides compute and we don't charge for CPU wait time, so bills are a lot cheaper with our solution.

Re: Show HN: Inngest 1.0 – Open-source durable workflows on every platform

#42
post #18
post #15

Earlier quoted context omitted.

And it seems their misnomer is practically everywhere, not just in the Show HN: their website also mislabels their links as "Open Source" - I guess trying to capitalize on SEO SSPLv1 for anyone similarly interested https://github.com/inngest/inngest/blob/v1.0.0/LICENSE.md Seems they had a change of heart around 2022: https://github.com/inngest/inngest/pull/81 but they actually only started lying about the license in…

We'll roll out a change that releases source as GPL after 3-4 years next week, actually. I do appreciate these comments and points.

So "eventually OSS"? That's certainly better, especially so for some use cases (company goes under), but it isn't OSS either.

Re: Show HN: Inngest 1.0 – Open-source durable workflows on every platform

#43

Looking at the License - This is not Open Source, but rather Source Available software. Looks great but do not appreciate deceptive marketing

I opened the comments before the website as I was sure this would be another of those sources available clickbait. Why is this kind of disingenuous move not enforced in the title guidelines of HN is beyond me.

Re: Show HN: Inngest 1.0 – Open-source durable workflows on every platform

#44
post #43

Looking at the License - This is not Open Source, but rather Source Available software. Looks great but do not appreciate deceptive marketing

I opened the comments before the website as I was sure this would be another of those sources available clickbait. Why is this kind of disingenuous move not enforced in the title guidelines of HN is beyond me.

[dead]

Re: Show HN: Inngest 1.0 – Open-source durable workflows on every platform

#45
post #18
post #15

Earlier quoted context omitted.

And it seems their misnomer is practically everywhere, not just in the Show HN: their website also mislabels their links as "Open Source" - I guess trying to capitalize on SEO SSPLv1 for anyone similarly interested https://github.com/inngest/inngest/blob/v1.0.0/LICENSE.md Seems they had a change of heart around 2022: https://github.com/inngest/inngest/pull/81 but they actually only started lying about the license in…

We'll roll out a change that releases source as GPL after 3-4 years next week, actually. I do appreciate these comments and points.

Why not dual license with AGPL?

Re: Show HN: Inngest 1.0 – Open-source durable workflows on every platform

#46

I've been looking into this space since I learned about Temporal recently, and I wonder if it would be better to have this integrated in my application, as a library, instead of an external dependency. This way, all the state would be in the same DB.

If your application is Python or TS based, you can check out the DBOS libraries, which do that.

No, they don't. They work just like Temporal and the others, which send the durable state to a separate store. I totally understand that this is good for the tool business model, since many users will end up paying for the separate store, instead of keeping it in the same DB where the application already is, without needing to pay extra for it. After all, the amount of data for keeping that state should be relativly small, so no one would provision a separate DB for it if the SDK didn't force them to.

Re: Show HN: Inngest 1.0 – Open-source durable workflows on every platform

#48
post #31

Earlier quoted context omitted.

And the production infra for running isn't even available, just a pared down "development server" via SSPL. This is a long way from OSS.

There might be a bit of misunderstanding on what's in that git repo here. It actually contains the executor, state store, queue, and our production UI, plus the syncing, registration, and logic for functions. Earlier this year we didn't want folks to roll their own production cloud due to queueing migrations. It would make your life hard. We're entirely responsible for that right now, as we discouraged self hosting.…

Let me know when you do! I like the pattern and APIs you've designed for the SDKs—and would probably rely on a managed coordination layer like you've got. But, in order to build confidence in any product like this, we have to know that if something happened to the co, or you went another direction, we could fork the core and continue on.

Re: Show HN: Inngest 1.0 – Open-source durable workflows on every platform

#50
post #18
post #15

Earlier quoted context omitted.

And it seems their misnomer is practically everywhere, not just in the Show HN: their website also mislabels their links as "Open Source" - I guess trying to capitalize on SEO SSPLv1 for anyone similarly interested https://github.com/inngest/inngest/blob/v1.0.0/LICENSE.md Seems they had a change of heart around 2022: https://github.com/inngest/inngest/pull/81 but they actually only started lying about the license in…

We'll roll out a change that releases source as GPL after 3-4 years next week, actually. I do appreciate these comments and points.

don't let that stop you from using it marketing though.. if you're misleading with your marketing it makes me wonder what else is not as it is claimed.
Post reply on HN