Home/Learn/Event Driven Architecture
Topic

Event Driven Architecture

Learn Event Driven Architecture as a connected topic across chapters, concepts, simulations, and interview reasoning.

10 Concepts7 Articles1h 42m

Overview

Learn Event Driven Architecture as a connected topic across chapters, concepts, simulations, and interview reasoning.

How this topic helps

System Design
Architecture
Distributed Systems
Data Engineering

Learning Path in this Topic

Series that contain articles from Event Driven Architecture. Select a path to filter the article list.

Articles

7 matched articles

Article 1System Design Message Queues and Event-Driven Architecture: Building Reliable Asynchronous SystemsTLDR: Message queues and event-driven architecture let services communicate asynchronously, absorb bursty traffic, and isolate failures. The core design challenge is not adding a queue — it is definin14 minArticle 2Stream Processing Pipeline Pattern: Stateful Real-Time Data ProductsTLDR: Stream pipelines succeed when event-time semantics, state management, and replay strategy are designed together — and Kafka Streams lets you build all three directly inside your Spring Boot serv15 minArticle 3Serverless Architecture Pattern: Event-Driven Scale with Operational GuardrailsTLDR: Serverless is strongest for spiky asynchronous workloads when cold-start, observability, and state boundaries are intentionally designed. TLDR: Serverless works best for spiky, event-driven wo13 minArticle 4Integration Architecture Patterns: Orchestration, Choreography, Schema Contracts, and Idempotent ReceiversTLDR: Integration failures usually come from weak contracts, unsafe retries, and missing ownership rather than from choosing the wrong transport. Orchestration, choreography, schema contracts, and ide15 minArticle 5Event Sourcing Pattern: Auditability, Replay, and Evolution of Domain StateTLDR: Event sourcing pays off when regulatory audit history and replay are first-class requirements — but it demands strict schema evolution, a snapshot strategy, and a framework that owns aggregate l15 minArticle 6Dead Letter Queue Pattern: Isolating Poison Messages and Recovering SafelyTLDR: A dead letter queue protects throughput by moving repeatedly failing messages out of the hot path. It only works if retries are bounded, triage has an owner, and replay is a deliberate workflow 14 min

Page 1 of 2