Loading content
Event-driven durable execution; steps, retries and flow control over a queue you don't manage. Best suited: Event-driven background jobs and durable multi-step functions without running your own queue. Watch out: Workflow infrastructure, not an agent framework — agent logic lives inside your step functions.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Inngest is a platform for event-driven functions, durable workflows, and background jobs.
Inngest grew from the need to build reliable background processes without maintaining queue and orchestration logic. Its open-source project and service developed event-based execution with retries, schedules, and state.
A function reacts to an event or schedule. Inngest stores the run, pauses at waits, retries failed steps, and resumes the workflow while the application supplies individual handlers.
It starts or influences a function.
A step encapsulates a repeatable operation.
Runs and waits survive process boundaries.
Inngest simplifies robust asynchronous flows. Idempotency, failure paths, state data, limits, and provider dependence belong in the architecture decision.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.