tomredman

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 beyond it just being Inngest"? I like to think I've been able to use it effectively without this having ever crossed my mind. But I also just might be dumb. Hence the curiosity!

Are there plans beyond workflow? (For context I enjoy Inngest already :)

Wow, I had no idea you weren’t at 1.0 yet lol. I’ve been using Inngest for a few years(!) and it’s always felt really polished and complete to me.

Congrats on the big one-oh. Question: I’ve been using Rust a lot more lately — does Inngest work natively with Rust? Is there an SDK or another way to use it?

Love to see this guys, great work and love to this pivot working for you.

Next June!

The timing of this is pretty awesome for me. I’m building a product that requires fairly heavy, scheduled background services. Originally, I had built these services intermingled with my client and API, but it was not ideal from a development or deployment process. Plus we had rolled our own monitoring which was itself a PITA to maintain. With Inngest, I moved all of our background services and processing to a separate sub-repo, and we can develop, deploy and monitor entirely independently from the rest of our product which has really sped things up. Love it. Would recommend for anything event-based!

The last straw for me was the few times I ran into issues, often due to my own mistakes, their support was nearly real-time and worked with me either help me solve the problem or dig in on their end to see where the issue was. Honestly more than anything the support gives me confidence to fully commit to this and use across all my production apps.

Anyway, great stuff all, you’ve built something awesome here.

I mean, this is true. But it’s weird being in the center of that raging fire. We were worried about getting sued personally (there were lots of threats) and or having our family or work brought it into it. Lots of people tried to get me fired. In the moment, it just wasn’t a fight we wanted to fight.

Yup I am. My point though is that that argument is largely underestimating the value delivered by these products. And the apparent lack of P/M fit for spreadsheets managing diversity at large companies.

People had the same arguments against Dropbox (just use rsync) and Buffer itself (just use a cronjob).

Not me :) I opted for the equity option. -Tom, Mobile Engineer @ Buffer