Inngest is the fastest way to orchestrate any async code. Wrap functions in steps that pause, fan-out, defer, retry, a/b test—one SDK, zero infra.
Worldwide
Joined May 2021
- Tweets1.3K
- Following114
- Followers6.2K
- Likes2K
Is your best customer getting held up by your worst?
Or to be less dramatic... are any of your users waiting for another user's long-running jobs to complete?
If so (and yes definitely if you're just using a basic queue), you have a noisy neighbor problem.
Inngest provides two important tools to help, that sometimes get confused:
1) 𝗖𝗼𝗻𝗰𝘂𝗿𝗿𝗲𝗻𝗰𝘆 𝗞𝗲𝘆𝘀: Decide who waits on whom
2) 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻: Let important work cut the line
Learn more 👉️ inngest.com/blog/long-runnin…
San Francisco: You know the post-lunch coffee that comes before the pre-dinner coffee? Tomorrow, that one's on us 🤑
We're taking over Corgi Cafe to fuel you for the lonng run.
Swing by, pick up a drink, meet the team, and leave with some sick swag designed by our very own Savannah Bergeron 💞
You MUST register to cop the goods 🤌 : luma.com/inngest-2gu5
𝗪𝗵𝗲𝗿𝗲, 𝘄𝗵𝗲𝗻, 𝗮𝗻𝗱 𝘄𝗵𝘆:
📍 Corgi Cafe | 9 Claude Lane, SF
🗓 Wednesday, October 21 | 12–2 PM
❓️ Bc we rly like u
Lonng-running humans. Lonng-running agents. 🏃
NYC brought the miles. We brought the caffeine.
Big thanks to the @foundersrc crew and everyone who showed up to build (and run) for the long run.
SF, you're up next. We've got a few things brewing for you this week. ☕ More details soon!
Our migration from Valkey to FoundationDB continues!
And part 2 in our series about how it's going is now live.
This post covers how work is laid out, how accounts move, and how we keep one busy account from crowding out everyone else.
inngest.com/blog/migration-t…
Inngest retweeted
I inherited a system that processed 100k medical records overnight. Here is what I learned about long-running, massive data jobs:
Inngest retweeted
How do you scale a long-running agent or multi-step workflow beyond the restrictive request limits of most serverless host providers?
Got a question about your workflows, but don't want to leave the CLI?
Inngest is now in the Claude Code plugin directory 🎉
/plugin install inngest@anthropic-plugin-directory
Ask things like,
❓️"Why is my research agent taking so long today?"
❓️"Why aren't new customers getting the welcome emails?"
Or initiate work like,
➡️ “Send a test order.created event to staging.”
➡️ “Cancel the runs from the import I started by mistake.”
Check out the docs for more!
A run is only as reliable as the work inside it, including the sandbox that tests the code.
Today's sandboxes live outside the durable execution chain. They can't see the run that called them, which means:
1) you're billed through its waits
2) durability is left to your code
Inngest Sandboxes, now in open beta on the TypeScript SDK, are simple steps, defined where your other durability primitives already live.
They survive crashes, pause on the run's waits, and cap at one hour of active runtime, so you never start from scratch or pay for a forgotten machine.
Get started today ➡️
Blog: inngest.com/blog/sandboxes-a…
Playground: inngest.com/try-sandboxes
3x concurrency when you need it most ↗️
Spikes are pretty unpredictable, but not a bad thing!
It usually just means your product is getting used more than you expected.
Bursty concurrency in Inngest raises your limit by 𝟯𝘅 as soon as a spike begins, so you (and your users) don't get throttled waiting for slots to open. This happens automatically, for up to an hour a month, at no additional charge.
Use it to right-size your concurrency ceiling so you don't punish users, or pay for what you don't need.
If you're thinking, what even is concurrency... have I got the animated explainer for you 🧵
Bursty concurrency changes what happens at that limit. Inngest will burst you 3x past your ceiling (as set by your current plan), for a total of one hour, every month. By running "surprise" work rather than letting it build a backlog, Inngest lets you:
1) Keep things moving when unexpected events occur.
2) Better assess what your monthly concurrency should be set to.
Get all the details in the blog:
inngest.com/blog/new-bursty-…
Have you submitted your build to our CodeTV Hackathon yet? 👀
Free Inngest + our most-requested swag is on the line!
inngest.com/events/codetv-we…
We went to Portland. We asked 3 teams to build something that keeps running while they do something else. Things got weird 😅
Our episode of the Web Dev Challenge is now live! Huge thanks to the whole crew, and our hilarious contestants 😆
youtu.be/pui1mW9sexM?si=IvqS…
If you want to partake in the weirdness, our hackathon is now open! Build something that runs while you're away (pauses, waits for events, retries automatically, etc) and win prizes.
inngest.com/events/codetv-we…
In 2020, Featured's "orchestration layer" was 8 people.
Now it's software — 7 people run 3 brands, shipping ~2,500 articles/month on deadline with @inngest.
How they built it (incl. the deliberately boring scheduler that makes it work): inngest.com/customers/featur…
Feature Friday: run priority
This week, we showed Inngest's queue is a tree sorted by time. The neat payoff: to make a job run sooner, you date its timestamp into the past.
inngest.com/docs/guides/prio…
