Reposted by Dan Farrelly - InngestSterling Chin @sterlingchin.bsky.social · 08/05/2026More engineers should mean more confidence. Right? We surveyed 130 engineers for the 2026 AI in Production benchmark. 26% of small teams are very confident at 2-3x scale. 13% of mid teams. 0% of teams with 500+ engineers. The gap isn't tooling. It's context across the stack. Link in thread ↓ 152
Reposted by Dan Farrelly - InngestFrontend Dogma @frontenddogma.com · 20/03/2026Node.js Worker Threads Are Problematic, but They Work Great for Us, by @inngest.com: www.inngest.com/blog/node-worker-th… #nodejs #workerthreads #eventloopinngest.comNode.js worker threads are problematic, but they work great for us - Inngest BlogWorker threads solve real problems, but they come with constraints that Go, Rust, and Python developers would never expect. Here's what we learned moving Inngest Connect's internals off the main thread. 031
Dan Farrelly - Inngest @danfarrelly.com · 31/01/2026It was a blast joining Jason for this podcast - a great lineup of initial guests too! Check it out ⬇️ 031
Dan Farrelly - Inngest @danfarrelly.com · 31/01/2026Hey Andrew! We’ll get that PR merged and released ASAP. I’ll take a look tomorrow. For the other issue, where are you seeing that? If you have an account on Inngest cloud, dm me your account email and I’ll check out the function config and see what’s up 010
Reposted by Dan Farrelly - InngestJason Lengstorf @jason.energy · 27/01/2026on Spotify there are video and audio options: open.spotify.com/show/1je9GKo...open.spotify.comHow to connect everything to everything with InngestSpotify video 101
Dan Farrelly - Inngest @danfarrelly.com · 26/11/2025media.tenor.comDis Belief Surprised GIFALT: Dis Belief Surprised GIF 000
Reposted by Dan Farrelly - InngestDigitalOcean @digitalocean.com · 06/11/2025Workflows made simple (& durable). 🤝🔗☁️ Inngest, a durable workflow orchestration platform, helps developers build scalable products, like AI workflows, agents, & e-commerce stores, without the complexity of managing infrastructure. ➡️ do.co/4oQGVPx 022
Dan Farrelly - Inngest @danfarrelly.com · 26/03/2025fetch the snapshots of the state from the API and push to the browser. We might explore some sort of long-term KV or state store in the future, but in the near term, I think this API would help - what do you think? 020
Dan Farrelly - Inngest @danfarrelly.com · 26/03/2025This makes sense - it's a cool approach. Our AgentKit library is doing something similar with state as well leveraging the output of steps to build up state. Ideally if state was persisted in the output of `step.run` and we added an API to query the output of each step you would be able to... 110
Dan Farrelly - Inngest @danfarrelly.com · 24/03/2025The Redis and pg URI options are documented here in our docs. We’d like to add a full docker compose example soon, but this should get you going. www.inngest.com/docs/self-ho...inngest.comSelf-hosting - Inngest DocumentationLearn how to self-host Inngest. Includes configuration options and instructions for using external services. 120
Dan Farrelly - Inngest @danfarrelly.com · 22/03/2025Yeah. That’s accurate. If you’re putting prod workloads on the self-host, I would run Redis and Postgres to back it instead of sqlite. You can also sign up for cloud for free to try things out pretty easily then move over to self -hosted later if you want. 110
Dan Farrelly - Inngest @danfarrelly.com · 22/03/2025Anything in particular that you’re curious about? 110
Dan Farrelly - Inngest @danfarrelly.com · 22/03/2025We should create a comparison table for reference, but our newest features like realtime and “connect” are also in self-hosted setup although may require some configuration. Self-hosting continues to get new benefits every week as that’s where our team commits our core code 120
Dan Farrelly - Inngest @danfarrelly.com · 22/03/2025It can be used in prod and devs are doing that today. It does not have feature parity with cloud though. It doesn’t have the o11y metrics dashboard, auth and bulk actions like replay or cancellation. All flow control and queueing are core to the self-hosted setup so execution is exactly the same! 120
Dan Farrelly - Inngest @danfarrelly.com · 21/03/2025coffee shop putting death cab and new bad bunny back to back, ideal for reaching flow this morning 020
Reposted by Dan Farrelly - InngestDirectus @directus.io · 19/03/2025Tomorrow we're teaming up with our friends at Inngest! Learn how to build a content localization engine that instantly translates all of your content into whatever languages you'd like when you hit save 👉 RSVP for the workshop: directus.is/workshop/in... 153
Dan Farrelly - Inngest @danfarrelly.com · 19/03/2025Love starting the day and seeing messages like this in our Discord. Fuel for the day! 040
Dan Farrelly - Inngest @danfarrelly.com · 14/03/2025Awesome - ping me here or on our Discord with any feedback - we'd love thoughts on how to smooth out the API and things that might help you reduce boilerplate, etc. 120
Dan Farrelly - Inngest @danfarrelly.com · 14/03/2025Funny you should ask about hooks and realtime... www.inngest.com/docs/feature... (this developer preview just went live 2 days ago; haven't promoted it) What do you think? We do need more examples, but we're iterating on APIs and hooks to make it as ergonomic as possible. Would love your feedback!inngest.comRealtime - Inngest DocumentationLearn how to use realtime to stream data from workflows to your users. 130
Dan Farrelly - Inngest @danfarrelly.com · 11/03/2025They’re selling Girl Scout cookies at the brewpub. This is genius, these girls are gonna sell so many boxes. Everyone is buying, including me. 010
Dan Farrelly - Inngest @danfarrelly.com · 07/03/2025durable execution is an abstraction, not the end goal. 000
Dan Farrelly - Inngest @danfarrelly.com · 01/03/2025I would love to layer on more ways to use Inngest’s primitives over time, like how we’re doing with AgentKit. I think as we’ve seen several other companies adopt the step/context.run model after Inngest tools could also be interoperable. 010
Dan Farrelly - Inngest @danfarrelly.com · 01/03/2025Yeah, that’s interesting. Maybe workflow kit needs to be more composable and kinda of like a portable format like it can be an output and an input whereas Inngest function outputs and trace visualizations now cannot be inputs. 210
Dan Farrelly - Inngest @danfarrelly.com · 28/02/2025Maybe this is a bad path the more I look at things. 🙈 000
Dan Farrelly - Inngest @danfarrelly.com · 28/02/2025I know this is asking a lot, but is there an example in the docs that matches your workflow most closely? Not sure if this is a good approach, but I was looking for a way to hook into the xstate execution loop and inject Inngest's step.run into there. 210
Dan Farrelly - Inngest @danfarrelly.com · 28/02/2025That's helpful. I have to admit that I'm not very well accustom to xstate and just took a look at it for a few minutes to explore how we might map it to Inngest and there are so many ways to create state machines in xstate it's hard to find a clean path to map to 210
Dan Farrelly - Inngest @danfarrelly.com · 28/02/2025Ah ok - that's the main main value for you w/ xstate? the visual side of seeing it ahead of time? 100
Dan Farrelly - Inngest @danfarrelly.com · 27/02/2025Is that what you're thinking more or less? How would you wanna write this, with a state machine, a DAG or just in code with a kind of "router" function? Also, are you looking for functions that kind of run forever or something that is mostly executing to completion? 200
Dan Farrelly - Inngest @danfarrelly.com · 27/02/2025This is interesting, we have modeled ideas like this, especially for AI use case where each step.run within an Inngest function returns the current state of the entire workflow (like a DO) then the loop takes that current state and decides what to run next, returning the state. 210
Dan Farrelly - Inngest @danfarrelly.com · 26/02/2025This is insane level of TypeScript. Really a fun watch and some awesome how-we-did it context from Dimitri. I love this. www.youtube.com/watch?v=0mCs...youtube.comTypeScript types can run DOOMYouTube video by Michigan TypeScript 030
Dan Farrelly - Inngest @danfarrelly.com · 21/02/2025At the end of the day, it's all highly dependent on your use case though, what are you building? 100
Dan Farrelly - Inngest @danfarrelly.com · 21/02/2025Lastly, Inngest has great coverage from our local dev server which runs on your machine for fast iteration and cloud observability with metrics and traces. Your code can run on any cloud or infra and it scales to billions of executions a month. 110
Dan Farrelly - Inngest @danfarrelly.com · 21/02/2025As it's event driven, Inngest can receive events from your application or webhooks to trigger workflows and the events are utilized on recovery tooling like bulk replay if you have a bug or third party API issue that you need to recover from. www.inngest.com/docs/platfor... 100
Dan Farrelly - Inngest @danfarrelly.com · 21/02/2025Inngest's SDKs all work with a very flexible "step" construct that makes it easy to define workflows in very normal looking code that can also generate new steps at runtime. This makes it ideal for workflows that are dynamic like AI agents or for building user-generated workflow systems. 110
Dan Farrelly - Inngest @danfarrelly.com · 21/02/2025I'm not an expert on DBOS and it's new-ish, so it will be hard for me to compare, but at it's core, Inngest is event-driven and has a custom-built queue that includes multi-tenant aware flow control functionality that handles complex concurrency, throttling, etc... www.inngest.com/docs/guides/... 210
Dan Farrelly - Inngest @danfarrelly.com · 18/02/2025Today prom metrics, more coming soon in this space... 030
Reposted by Dan Farrelly - InngestArne Wiese @wiesson.bsky.social · 27/01/2025We are using inngest and it just works. I had 80k+ items to enqueue and it was no problem at all :) 251
Dan Farrelly - Inngest @danfarrelly.com · 27/01/2025Awesome work! Love to see it all come together 👏 120
Dan Farrelly - Inngest @danfarrelly.com · 27/01/2025You’ve likely already looked into this, but you can migrate an Inngest app across cloud providers so you could shift to a containerized platform if that’s better for your workload like Render, Fly or ECS. It should be a matter to redeploying and updating the URL on your next sync. Lmk if I can help! 020
Reposted by Dan Farrelly - Inngestskyrocketgg.bsky.social @skyrocketgg.bsky.social · 08/01/2025event matching with inngest is amazing 011
Dan Farrelly - Inngest @danfarrelly.com · 26/01/2025Thanks for the feedback. We’ll work on improving this! 020
Dan Farrelly - Inngest @danfarrelly.com · 26/01/2025Nice! Looks great! Let us know if we could provide any better docs for middleware or types! 120
Dan Farrelly - Inngest @danfarrelly.com · 24/01/2025⬇️ new tutorial to check out for some Friday afternoon and weekend projects 011
Dan Farrelly - Inngest @danfarrelly.com · 21/01/2025For now, CRUD apps are easy mode for AI code writers, but I still needed some context to know what to prompt it. Not much though! 010
Dan Farrelly - Inngest @danfarrelly.com · 21/01/2025Built my first end to app with Cursor this weekend using a next starter as the base. I get the hype now. Composer is legit. It naturally struggled with time zone issues and plenty of duplicate code, but would have replaced a lot of work done by the first agency I worked for. 140
Dan Farrelly - Inngest @danfarrelly.com · 15/01/2025Durable functions/workflows/execution are interesting, but also pretty simple. Sometimes I wish I had a few weeks to record videos and tutorials on how it works and how to do it yourself. 010
Dan Farrelly - Inngest @danfarrelly.com · 11/01/2025Middleware could be an interesting idea. Either hooking directly into the lifecycle of steps/executing to trigger WS messages or automatically injecting the WS client/helpers: www.inngest.com/docs/feature...inngest.comUsing Middleware for Dependency Injection - Inngest DocumentationInngest documentation for Using Middleware for Dependency Injection 230
Dan Farrelly - Inngest @danfarrelly.com · 11/01/2025Are you explicitly pushing certain steps or updates to the client? Any fun code with Inngest, Inngest middleware or mostly mid-function calls to Azure Web Pub Sub 130