<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/building-an-event-driven-queue-based-on-common-standards-asoyfccnz" -->

---
title: Building an event-driven queue based on common standards
description: An engineering team at Inngest explains why they built a new event-driven queueing platform instead of using existing tools like SQS/Lambda or Pub/Sub. They...
canonical: https://daily.dev/posts/building-an-event-driven-queue-based-on-common-standards-asoyfccnz
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Building an event-driven queue based on common standards | daily.dev
og:description: An engineering team at Inngest explains why they built a new event-driven queueing platform instead of using existing tools like SQS/Lambda or Pub/Sub. They...
og:url: https://daily.dev/posts/building-an-event-driven-queue-based-on-common-standards-asoyfccnz
og:image: https://api.daily.dev/og/posts/aSOYfccNZ.png
og:image:alt: Building an event-driven queue based on common standards
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Building an event-driven queue based on common standards

**[Inngest Blog](https://daily.dev/sources/inngest)** · 8 min read · 0 upvotes · 0 comments

## Summary

An engineering team at Inngest explains why they built a new event-driven queueing platform instead of using existing tools like SQS/Lambda or Pub/Sub. They walk through the design philosophy of moving from RPC-style queues to event-driven contracts, enabling declarative functions, DAG-based steps, versioned typed events, blue-green deploys, historical replay, and complex multi-step coordination without requiring an SDK. Events are sent via plain JSON over HTTP, functions can run on Lambda, Docker, or other runtimes, and the execution engine, drivers, and state layers are open sourced on GitHub.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.inngest.com/blog/building-an-event-driven-queue>

## Questions this post answers

### What is the difference between building a queue as event-driven versus RPC-style?

An event-driven queue decouples the callsite, the specific queue, and the function by using a strongly typed event as the contract, rather than treating the queue as an eventual RPC call. This lets you enforce and version event schemas, make functions declarative by specifying which events trigger them, and add features like blue-green deploys and historical replay without changing core services.

_Developers weighing queueing architectures can find these design trade-offs curated on daily.dev._

### How do you define a multi-step function without using an SDK in Inngest?

Functions are defined as JSON with a name, id, one or more triggers (events with optional conditional expressions), and steps that form a DAG, each with its own runtime such as docker or lambda and an 'after' field for ordering. Event and function context are passed as arguments and step output is read from stdout, so no SDK or special libraries are required in any language.

_Engineers building async workflows can track approaches like this one on daily.dev._

## Similar posts on daily.dev

- [The Complete Guide to Message Queues and Event Streaming: Building Scalable, Reliable, and Real-Time Distributed Systems](https://daily.dev/posts/the-complete-guide-to-message-queues-and-event-streaming-building-scalable-reliable-and-real-time-72zillsk8) · Medium · 0 upvotes · 0 comments
- [Patterns & Best Practices in Event-Driven Systems — Kogan.com Dev Blog](https://daily.dev/posts/patterns-best-practices-in-event-driven-systems-kogan-com-dev-blog-klr34bwfw) · Kogan.com · 44 upvotes · 2 comments
- [Building a Global, Event-Driven Platform: Our Ongoing Journey, Part 1](https://daily.dev/posts/building-a-global-event-driven-platform-our-ongoing-journey-part-1-yeyp1crv1) · Vinted · 0 upvotes · 0 comments
- [Introducing enhanced custom event buses in Amazon EventBridge for enterprise-scale event-driven applications](https://daily.dev/posts/introducing-enhanced-custom-event-buses-in-amazon-eventbridge-for-enterprise-scale-event-driven-appl-xeruwr81i) · AWS · 0 upvotes · 0 comments

---

Tags: [#architecture](https://daily.dev/tags/architecture), [#inngest](https://daily.dev/tags/inngest), [#serverless](https://daily.dev/tags/serverless), [#system-design](https://daily.dev/tags/system-design)

[View this post on daily.dev](https://daily.dev/posts/building-an-event-driven-queue-based-on-common-standards-asoyfccnz)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Building an event-driven queue based on common standards","url":"https://daily.dev/posts/building-an-event-driven-queue-based-on-common-standards-asoyfccnz","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/building-an-event-driven-queue-based-on-common-standards-asoyfccnz"},"datePublished":"2026-09-13T19:57:49.738Z","dateModified":"2026-11-01T18:46:45.913Z","description":"An engineering team at Inngest explains why they built a new event-driven queueing platform instead of using existing tools like SQS/Lambda or Pub/Sub. They...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ba934223c60123db4073182ed588575?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ba934223c60123db4073182ed588575?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Inngest Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Inngest Blog","logo":"https://media.daily.dev/image/upload/s--ieZKUa5y--/c_limit,w_256/f_auto,q_auto/v1789329423/logos/inngest?_a=BAMAMicg0","url":"https://daily.dev/sources/inngest"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/building-an-event-driven-queue-based-on-common-standards-asoyfccnz","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"architecture,inngest,serverless,system-design","timeRequired":"PT8M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Inngest Blog","item":"https://daily.dev/sources/inngest"},{"@type":"ListItem","position":3,"name":"Building an event-driven queue based on common standards"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/building-an-event-driven-queue-based-on-common-standards-asoyfccnz#faq","mainEntity":[{"@type":"Question","name":"What is the difference between building a queue as event-driven versus RPC-style?","acceptedAnswer":{"@type":"Answer","text":"An event-driven queue decouples the callsite, the specific queue, and the function by using a strongly typed event as the contract, rather than treating the queue as an eventual RPC call. This lets you enforce and version event schemas, make functions declarative by specifying which events trigger them, and add features like blue-green deploys and historical replay without changing core services. Developers weighing queueing architectures can find these design trade-offs curated on daily.dev."}},{"@type":"Question","name":"How do you define a multi-step function without using an SDK in Inngest?","acceptedAnswer":{"@type":"Answer","text":"Functions are defined as JSON with a name, id, one or more triggers (events with optional conditional expressions), and steps that form a DAG, each with its own runtime such as docker or lambda and an 'after' field for ordering. Event and function context are passed as arguments and step output is read from stdout, so no SDK or special libraries are required in any language. Engineers building async workflows can track approaches like this one on daily.dev."}}]}
```

