[shawnb576]

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

[danfarrelly]

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.