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

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

inngest.com

Post reply on HN
Print view View original

31–40 of 55 posts

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

#31

Post by tonyhb »

lgsilver wrote: post #28
mdaniel wrote: 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…

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.

That's actually coming to a close, and we'll make it easy to spin up prod clusters using this code and eg. MemoryDB, Dragonfly, or what have you.

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

#32

Post by davekiss »

I implemented Inngest to handle our video migration queues that help move videos off of other platforms into Mux -- complete breeze. Loved the balance between the amount of complexity that's abstracted away, but still enough of a surface API exposed to do some pretty custom domain-specific work. Also the support was top notch, that goes a long way. A++, would use again, genuinely a fan.

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

#34

Post by Onawa »

tonyhb wrote: post #18
mdaniel wrote: 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 is it necessary to wait? You've already seen the feedback, if you're going to change the license, why promise to do it later?

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

#35

Post by [deleted] »

Onawa wrote: post #34
tonyhb wrote: post #18

Earlier quoted context omitted.

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 is it necessary to wait? You've already seen the feedback, if you're going to change the license, why promise to do it later?

[deleted]

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

#36

Post by tonyhb »

Onawa wrote: post #34
tonyhb wrote: post #18

Earlier quoted context omitted.

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 is it necessary to wait? You've already seen the feedback, if you're going to change the license, why promise to do it later?

It's already planned, and rushing out a legal change on a Friday night ahead of plans is less than ideal.

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

#37

Post by tonyhb »

Shakahs wrote: post #33

Restate.dev seems to offer a different implementation of the same feature set, and I think I might like their durable execution syntax more.

Their syntax does look strikingly similar to the API we launched with a couple of years ago: `ctx.run("id", () => {})` vs `step.run("id", () => {})`.

It's good to see the ecosystem form around the APIs we've developed. From feedback we've received, they're easy to use.

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

#38

Post by giovannibonetti »

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.

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

#39

Post by secondrow »

giovannibonetti wrote: post #38

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.

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

#40

Post by zx8080 »

tonyhb wrote: post #18
mdaniel wrote: 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.

Is there any guarantee ("don't take promise from a company") the license won't be changed to something more closed some time afterwards?
Post reply on HN