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

31–37 of 37 posts

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

#31

Post by throwawaymaths »

darwin67 wrote: post #26
throwawaymaths wrote: post #22

Earlier quoted context omitted.

Just fyi: Neither are critical but I recommend your repo have underscore instead of hyphen for an elixir project, and using "ex" in the name of your project is generally (informally) considered to be a signal for low code quality in the community.

Thanks for the note, it's changed to underscore now. Regarding the "ex" prefix, it's a common pattern for Elixir libraries. https://github.com/h4cc/awesome-elixir

I'm just relaying stuff that is quietly joked about at elixir conferences. Take it or leave it.

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

#32

Post by danfarrelly »

hoofhearted wrote: post #30
danfarrelly wrote: post #2

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

What's the best way to go about getting Guillermo's attention?

Funny enough, we were fortunate to meet Guillermo through our lead, GGV as part of due diligence. GGV had recently led Vercel's recent round so he was part of the process of vetting our product. Our timing was also great as we had recently shipped our Vercel integration [1] and were the only integration supporting background jobs and workflows in their integration marketplace. He quickly recognized the value in what we were building and was interested to invest. It was an ideal combination of timing of having built something of value to the Vercel ecosystem and being intro'd!

Guillermo has been a fantastic supporter overall :)

[1] https://vercel.com/integrations/inngest

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

#34

Post by belmont_sup »

sv123 wrote: post #20
aliasxneo wrote: post #14

Earlier quoted context omitted.

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.

Isn’t life with aspnet easy enough because it actually can do multithreaded work right? So not really a problem for dotnet folks.

Unless you really want the one-click experience. We use aws sdk, spin up sqs, add some env vars to aspnet, connect the client, enqueue and dequeue all from the same app without a 3rd party (short of the queue infra).

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

#35

Post by shawnb576 »

danfarrelly wrote: post #24
radiospiel wrote: post #6

how does inngest compare to temporal?

Hey thanks for the comparison - Temporal is a powerful tool. There are definitely similarities with what Inngest is capable of. Here are a few differences to highlight: - We’ve taken a different approach that removes the queue and worker abstraction from the end developer and instead uses an HTTP-based invocation. This enables Inngest functions to be run on any platform, including serverless. - Inngest is powered by…

Temporal is designed for industrial strength flows and scale. For example an HTTP based push mechanism can overload workers hence the queue.

And its jusr code so not sure about the DSL reference (of course thats common with other systems)?

What use cases is this designed for? Easier to learn and build usually has tradeoffs

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

#36

Post by danfarrelly »

shawnb576 wrote: post #35
danfarrelly wrote: post #24

Earlier quoted context omitted.

Hey thanks for the comparison - Temporal is a powerful tool. There are definitely similarities with what Inngest is capable of. Here are a few differences to highlight: - We’ve taken a different approach that removes the queue and worker abstraction from the end developer and instead uses an HTTP-based invocation. This enables Inngest functions to be run on any platform, including serverless. - Inngest is powered by…

Temporal is designed for industrial strength flows and scale. For example an HTTP based push mechanism can overload workers hence the queue. And its jusr code so not sure about the DSL reference (of course thats common with other systems)? What use cases is this designed for? Easier to learn and build usually has tradeoffs

Inngest has built in concurrency controls and rate limiting to prevent systems from being overloaded, allowing the user to have the same controls of a traditional worker, but just a simple config option.

Inngest was designed to be a solution that can replace traditional queuing systems and event driven systems. Originally, it was built with the idea to handle complex flows that need to be durable, e.g. healthcare workflows that have time-based follow ups and legal compliance tasks that need to be executed in a specific order depending on patient confirmation or other actions.

We've seen users build all sorts of things: automate infrastructure based on events, building AI Agents around LLMs, perform vulnerability scans across thousands of packages, building scheduling products, and e-commerce data pipelines. We're seeing new use cases each week.

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

#37

Post by danfarrelly »

upmostly wrote: post #33

Used Inngest a few months ago and now use it, with RedwoodJS as part of every project I work on. It makes absolute sense to "event everything". Also, the dev-ex is incredible. Especially in conjunction with RedwoodJS. Well done, chaps!

Thanks! RedwoodJS is fantastic and we've been fortunate to collaborate with the core team to build in some great support for Inngest :)

We also collaborated with their core team on a GraphQL envelop plugin that automatically sends events for every mutation called in your api: https://github.com/inngest/envelop-plugin-inngest

Post reply on HN