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

Inngest raises $3M seed to build the reliable workflow platform for every dev

inngest.com

Post reply on HN
Print view View original

11–20 of 37 posts

Re: Inngest raises $3M seed to build the reliable workflow platform for every dev

#11

Post by tonyhb »

hobofan wrote: post #10

"every dev" = every JS/TS dev I'm not sure when it started, but I feel like there has been an recent increase of "for every dev" or "for everyone" in marketing copy of tools like these. Though, if you look into it for just a minute it's not a polyglot tool that at the core exposes e.g. a REST API that could be talked to in any language, but a "library + SaaS" for a very specific subset of developers (though not a sma…

Hah, I get it. We actually have an alpha Go SDK out, and an Elixir SDK in progress. The cool thing is you can switch languages and clouds, deploy a new endpoint, and function state carries over for zero downtime migrations.

https://github.com/inngest/inngestgo

https://github.com/darwin67/ex-inngest

Re: Inngest raises $3M seed to build the reliable workflow platform for every dev

#13

Post by _ktx2 »

hobofan wrote: post #10

"every dev" = every JS/TS dev I'm not sure when it started, but I feel like there has been an recent increase of "for every dev" or "for everyone" in marketing copy of tools like these. Though, if you look into it for just a minute it's not a polyglot tool that at the core exposes e.g. a REST API that could be talked to in any language, but a "library + SaaS" for a very specific subset of developers (though not a sma…

I think a lot of these early companies have high ambitions in terms of serving various languages, then they find out how hard writing SDKs and tooling for each of them is.

Re: Inngest raises $3M seed to build the reliable workflow platform for every dev

#14

Post by aliasxneo »

hobofan wrote: post #10

"every dev" = every JS/TS dev I'm not sure when it started, but I feel like there has been an recent increase of "for every dev" or "for everyone" in marketing copy of tools like these. Though, if you look into it for just a minute it's not a polyglot tool that at the core exposes e.g. a REST API that could be talked to in any language, but a "library + SaaS" for a very specific subset of developers (though not a sma…

Yeah, this has been pretty universal, lately. As a primarily Go/Rust/Python developer, it continues to baffles me how these languages continue to be the "default."

Re: Inngest raises $3M seed to build the reliable workflow platform for every dev

#15

Post by goodoldneon »

hobofan wrote: post #10

"every dev" = every JS/TS dev I'm not sure when it started, but I feel like there has been an recent increase of "for every dev" or "for everyone" in marketing copy of tools like these. Though, if you look into it for just a minute it's not a polyglot tool that at the core exposes e.g. a REST API that could be talked to in any language, but a "library + SaaS" for a very specific subset of developers (though not a sma…

Inngest engineer here!

We started with the TypeScript SDK to help us stay focused while we iterated and learned. As Tony said, we'll gradually expand to other languages (likely Python in the near future too!).

As for your "REST API instead of an SDK" concern, we invoke your functions so we need some code in your app. We need to handle things like memoizing steps within a function, so there needs to be some orchestration within the app

Re: Inngest raises $3M seed to build the reliable workflow platform for every dev

#16

Post by danfarrelly »

ravivyas wrote: post #4
danfarrelly wrote: post #2

Inngest co-founder here - happy to answer any questions about Inngest or our fundraising!

Congrats on the funding Typo on this line Your CI/CD process remains the same as before and Inngest

Thanks! Fixed :)

Re: Inngest raises $3M seed to build the reliable workflow platform for every dev

#17

Post by vikp »

tonyhb wrote: post #7
vikp wrote: post #5

I think this is an interesting service, and could be a nice way to write a SvelteKit or Next.js app with background workers. The press release is unnecessarily hyperbolic, which turned me off, though: > Deploying new jobs to production also requires tedious configuration of cloud infrastructure which often requires a handoff to another team or individual. Often weeks of developer time is spent on basic workflows, bef…

The simple case is simple, but anything beyond that can get challenging. Some examples: Multi-step functions. This requires chained jobs, and your dependencies get messy. Operating this kind of sucks. Change management here is hard. It's much easier and faster to write a single function using Inngest; basically any engineer can do it without learning infrastructure. Absence of events/activity (eg. when a user adds a…

I actually agree, which is why I wrote the comment. It is easy to create background tasks. Dramatiq can even handle some of the cases you mentioned - multi-step, fan-out, and retries.

It is hard to scale background tasks when you hit a high level of concurrency, as you've mentioned.

Your press releases makes it sound like the initial setup of background tasks is hard, and doesn't mention the harder stuff.

Re: Inngest raises $3M seed to build the reliable workflow platform for every dev

#18

Post by gumby »

hobofan wrote: post #10

"every dev" = every JS/TS dev I'm not sure when it started, but I feel like there has been an recent increase of "for every dev" or "for everyone" in marketing copy of tools like these. Though, if you look into it for just a minute it's not a polyglot tool that at the core exposes e.g. a REST API that could be talked to in any language, but a "library + SaaS" for a very specific subset of developers (though not a sma…

Thank you.

Re: Inngest raises $3M seed to build the reliable workflow platform for every dev

#19

Post by goodoldneon »

_ktx2 wrote: post #13
hobofan wrote: post #10

"every dev" = every JS/TS dev I'm not sure when it started, but I feel like there has been an recent increase of "for every dev" or "for everyone" in marketing copy of tools like these. Though, if you look into it for just a minute it's not a polyglot tool that at the core exposes e.g. a REST API that could be talked to in any language, but a "library + SaaS" for a very specific subset of developers (though not a sma…

I think a lot of these early companies have high ambitions in terms of serving various languages, then they find out how hard writing SDKs and tooling for each of them is.

> ... they find out how hard writing SDKs and tooling for each of them is.

Absolutely. Each additional SDK adds a lot of maintenance effort. It isn't just a write-it-once thing: - More time spent writing/updating docs - More context switching in support channels - More time spent updating SDKs as new features are developed

Staying focused on one SDK helps to keep velocity high in the early stages. But our product has matured enough that we feel comfortable gradually rolling out more language support, starting with Go soon

Re: Inngest raises $3M seed to build the reliable workflow platform for every dev

#20

Post by sv123 »

aliasxneo wrote: post #14
hobofan wrote: post #10

"every dev" = every JS/TS dev I'm not sure when it started, but I feel like there has been an recent increase of "for every dev" or "for everyone" in marketing copy of tools like these. Though, if you look into it for just a minute it's not a polyglot tool that at the core exposes e.g. a REST API that could be talked to in any language, but a "library + SaaS" for a very specific subset of developers (though not a sma…

Yeah, this has been pretty universal, lately. As a primarily Go/Rust/Python developer, it continues to baffles me how these languages continue to be the "default."

.net developer sitting over here in the corner watching all the cool things pass by.
Post reply on HN