# event-driven-architecture

Published articles for event-driven-architecture.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Your event-driven architecture is a distributed monolith -- and that's fine, if you measure it

DevFeed: [Your event-driven architecture is a distributed monolith -- and that's fine, if you measure it](<https://devfeed.tech/articles/your-event-driven-architecture-is-a-distributed-monolith-and-that-s-fine-if-you-measure-it-38795.md>)

Original publisher: [Read original article](<https://fidelitas.io/2026/05/event-driven-distributed-monolith/>)

Author: fidelitas.io

Published: 2026-05-15T10:30:00Z

Content type: opinion

Language: en

Sources: [fidelitas.io](<https://devfeed.tech/sources/fidelitas-io.md>)

Topics: [event driven](<https://devfeed.tech/topics/event-driven.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [Structured-data](<https://devfeed.tech/topics/structured-data.md>), [Traces](<https://devfeed.tech/topics/traces.md>), [interface](<https://devfeed.tech/topics/interface.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [coupling](<https://devfeed.tech/tags/coupling.md>), [decoupling](<https://devfeed.tech/tags/decoupling.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [event-driven-architecture](<https://devfeed.tech/tags/event-driven-architecture.md>), [messaging](<https://devfeed.tech/tags/messaging.md>), [observability](<https://devfeed.tech/tags/observability.md>), [schemas](<https://devfeed.tech/tags/schemas.md>), [services](<https://devfeed.tech/tags/services.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

This opinion article argues that event-driven systems can become distributed monoliths when message brokers hide rather than remove coupling. It focuses on explicit, versioned, validated schemas and traces as ways to reveal dependencies and diagnose failures.

### Source excerpt

Async messaging didn't decouple your services; it hid the coupling. Here's how to find the seams again with traces, schemas, and a healthy fear of fan-out.

## Event-Driven Architecture with Apache Kafka

DevFeed: [Event-Driven Architecture with Apache Kafka](<https://devfeed.tech/articles/mastering-event-driven-architecture-with-apache-kafka-39559.md>)

Original publisher: [Read original article](<https://ankit-rana.com/logs/07-kafka-event-driven-architecture/>)

Author: hello@ankit-rana.com

Published: 2026-03-16T00:00:00Z

Content type: tutorial

Language: en

Sources: [Ankit Rana | Mechanical Sympathy](<https://devfeed.tech/sources/ankit-rana-mechanical-sympathy.md>)

Topics: [event driven](<https://devfeed.tech/topics/event-driven.md>), [Kafka](<https://devfeed.tech/topics/kafka.md>), [Apache-Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [streaming-data-processing](<https://devfeed.tech/topics/streaming-data-processing.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [systems](<https://devfeed.tech/topics/systems.md>)

Tags: [apache-kafka](<https://devfeed.tech/tags/apache-kafka.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [consumer](<https://devfeed.tech/tags/consumer.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [event-driven-architecture](<https://devfeed.tech/tags/event-driven-architecture.md>), [event-sourcing](<https://devfeed.tech/tags/event-sourcing.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [partitions](<https://devfeed.tech/tags/partitions.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [schemas](<https://devfeed.tech/tags/schemas.md>), [stream-processing](<https://devfeed.tech/tags/stream-processing.md>)

### AI overview

This tutorial explains event-driven architecture and how Apache Kafka supports asynchronous, real-time data processing. It covers producers, consumers, immutable events, event sourcing, scalability, resilience, stream-processing pipelines, and challenges such as ordering, debugging, and eventual consistency.

### Source excerpt

Event-driven architecture replaces synchronous point-to-point calls with immutable events on a durable log, so producers and consumers scale and fail independently. Kafka provides that log: topics sharded into ordered append-only partitions, replicated across brokers, with consumer groups sharing partitions to scale read throughput.

## System Migration: Minimize Downtime, Maximize Efficiency

DevFeed: [System Migration: Minimize Downtime, Maximize Efficiency](<https://devfeed.tech/articles/system-migration-minimize-downtime-maximize-efficiency-39555.md>)

Original publisher: [Read original article](<https://ankit-rana.com/logs/03-system-migration/>)

Author: hello@ankit-rana.com

Published: 2026-03-16T00:00:00Z

Content type: tutorial

Language: en

Sources: [Ankit Rana | Mechanical Sympathy](<https://devfeed.tech/sources/ankit-rana-mechanical-sympathy.md>)

Topics: [migration](<https://devfeed.tech/topics/migration.md>), [systems](<https://devfeed.tech/topics/systems.md>), [async](<https://devfeed.tech/topics/async.md>), [client](<https://devfeed.tech/topics/client.md>), [event driven](<https://devfeed.tech/topics/event-driven.md>), [Kafka](<https://devfeed.tech/topics/kafka.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [apache-kafka](<https://devfeed.tech/tags/apache-kafka.md>), [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [async](<https://devfeed.tech/tags/async.md>), [bridge-layer](<https://devfeed.tech/tags/bridge-layer.md>), [data-pipelines](<https://devfeed.tech/tags/data-pipelines.md>), [downtime](<https://devfeed.tech/tags/downtime.md>), [event-driven-architecture](<https://devfeed.tech/tags/event-driven-architecture.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [migration](<https://devfeed.tech/tags/migration.md>), [observability](<https://devfeed.tech/tags/observability.md>), [production](<https://devfeed.tech/tags/production.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [rollback](<https://devfeed.tech/tags/rollback.md>), [system-migration](<https://devfeed.tech/tags/system-migration.md>), [traffic-leakage](<https://devfeed.tech/tags/traffic-leakage.md>)

### AI overview

A practical guide to migrating an existing system with minimal disruption. It recommends isolated-environment testing, load testing, adapters for incompatible contracts, synchronized asynchronous pipelines, a Kafka-based shared stream, a bridge layer, staged traffic switching, monitoring, and rollback preparation.

### Source excerpt

Migrate behind a bridge layer that routes all client traffic and supports three modes: old-only, dual, and new-only. Run dual mode to compare responses without user impact, keep a back-sync pipeline so the old system stays current for rollback, and shift traffic in stages while watching metrics at each step.

## Building resilient event-driven architecture for finance with Temporal

DevFeed: [Building resilient event-driven architecture for finance with Temporal](<https://devfeed.tech/articles/building-resilient-event-driven-architecture-for-finance-with-temporal-35750.md>)

Original publisher: [Read original article](<https://temporal.io/blog/building-resilient-event-driven-architecture-for-finserv-with-temporal>)

Author: Tim Imkin

Published: 2025-01-23T00:00:00Z

Content type: tutorial

Language: en

Sources: [Temporal Blog](<https://devfeed.tech/sources/temporal-blog.md>)

Topics: [event driven](<https://devfeed.tech/topics/event-driven.md>), [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [Orchestration](<https://devfeed.tech/topics/orchestration.md>), [reliability](<https://devfeed.tech/topics/reliability.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [Microservice](<https://devfeed.tech/topics/microservice.md>), [distributed-systems](<https://devfeed.tech/topics/distributed-systems.md>)

Tags: [business-logic](<https://devfeed.tech/tags/business-logic.md>), [coupling](<https://devfeed.tech/tags/coupling.md>), [crashes](<https://devfeed.tech/tags/crashes.md>), [databases](<https://devfeed.tech/tags/databases.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [error-handling](<https://devfeed.tech/tags/error-handling.md>), [event-driven-architecture](<https://devfeed.tech/tags/event-driven-architecture.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [retries](<https://devfeed.tech/tags/retries.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [temporal-concepts](<https://devfeed.tech/tags/temporal-concepts.md>)

### AI overview

This article examines the complexity of choreography-based event-driven architecture in financial services, including fragmented business logic, design-level coupling, decentralized error handling, and limited observability. It presents Temporal's durable execution and workflow orchestration as a centralized approach for building more resilient and maintainable systems.

### Source excerpt

Discover how Temporal simplifies event-driven systems, replacing complexity with scalability, reliability, and centralized workflows.

## Why Event-Driven Architecture Falls Short at Scale

DevFeed: [Why Event-Driven Architecture Falls Short at Scale](<https://devfeed.tech/articles/events-are-the-wrong-abstraction-rethinking-distributed-systems-35829.md>)

Original publisher: [Read original article](<https://temporal.io/blog/events-are-the-wrong-abstraction-rethinking-distributed-systems>)

Author: Drew Gorton

Published: 2024-11-12T08:00:00Z

Content type: article

Language: en

Sources: [Temporal Blog](<https://devfeed.tech/sources/temporal-blog.md>)

Topics: [distributed-systems](<https://devfeed.tech/topics/distributed-systems.md>), [event driven](<https://devfeed.tech/topics/event-driven.md>), [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [Microservice](<https://devfeed.tech/topics/microservice.md>), [reliability](<https://devfeed.tech/topics/reliability.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [event-driven-architecture](<https://devfeed.tech/tags/event-driven-architecture.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [temporal-concepts](<https://devfeed.tech/tags/temporal-concepts.md>)

### AI overview

This article argues that Event-Driven Architecture becomes complex, fragile, and difficult to manage at scale. It discusses unclear interfaces and effective coupling in EDA and presents Temporal's Durable Execution as an alternative perspective for simplifying distributed systems and improving reliability.

### Source excerpt

Discover why Event-Driven Architecture falls short at scale and how Durable Execution with Temporal simplifies distributed systems for better reliability.

## Replay 2023: Day one

DevFeed: [Replay 2023: Day one](<https://devfeed.tech/articles/replay-2023-day-one-35956.md>)

Original publisher: [Read original article](<https://temporal.io/blog/replay-day-one>)

Author: Rob Holland

Published: 2023-09-14T07:00:00Z

Content type: article

Language: en

Sources: [Temporal Blog](<https://devfeed.tech/sources/temporal-blog.md>)

Topics: [Development](<https://devfeed.tech/topics/development.md>), [event driven](<https://devfeed.tech/topics/event-driven.md>), [Code generation](<https://devfeed.tech/topics/code-generation.md>), [API](<https://devfeed.tech/topics/api.md>), [Kafka](<https://devfeed.tech/topics/kafka.md>), [Retool](<https://devfeed.tech/topics/retool.md>), [ordering](<https://devfeed.tech/topics/ordering.md>), [stripe](<https://devfeed.tech/topics/stripe.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [community](<https://devfeed.tech/tags/community.md>), [event-driven-architecture](<https://devfeed.tech/tags/event-driven-architecture.md>), [http](<https://devfeed.tech/tags/http.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [latency](<https://devfeed.tech/tags/latency.md>), [launches](<https://devfeed.tech/tags/launches.md>), [product-launches](<https://devfeed.tech/tags/product-launches.md>), [retool](<https://devfeed.tech/tags/retool.md>), [stripe](<https://devfeed.tech/tags/stripe.md>), [temporal](<https://devfeed.tech/tags/temporal.md>)

### AI overview

A recap of the first day of Replay 2023 covers Temporal's Durable Execution, product announcements, and customer presentations from Yum! Brands, Twilio, Retool, HashiCorp, and Stripe. The talks describe workflow migration, compliance adoption, DAG execution performance, code generation, and Kafka cluster management.

### Source excerpt

Replay 2023 Day 1 highlights: Temporal's Durable Execution, product launches, and insights from Yum! Brands, Twilio, Stripe, Datadog & more.