---
title: "Building an Event-Driven Architecture with Managed Data Services"
description: "Event-driven architecture (EDA) addresses the need to process and respond to continuous streams of real-time activity from applications, e-commerce systems, wearables, and other IoT sensors. Using Apache Kafka, independent producers publish events to topics while consumers subscribe and trigger downstream processes, keeping services decoupled and independently scalable. Kafka also distributes large data streams in real time and replicates data across synchronized broker nodes, so a node failure does not lose data or interrupt operation. Apache Kafka on Heroku is presented as a fully managed service, with multi-tenant basic and single-tenant private plans, automatic broker scaling, and Standard-tier-and-above configurations starting with three brokers and extending to eight. Recommended integration practices include mapping producer-consumer flows, using transactions, topic and schema management, and delivery guarantees, plus monitoring performance and logging Kafka operations."
---

# Building an Event-Driven Architecture with Managed Data Services

[Heroku](https://yomu.fyi/company/heroku) · Jonathan Brown · Aug 15, 2024

**Type:** Explainer

## Summary

Event-driven architecture (EDA) addresses the need to process and respond to continuous streams of real-time activity from applications, e-commerce systems, wearables, and other IoT sensors. Using Apache Kafka, independent producers publish events to topics while consumers subscribe and trigger downstream processes, keeping services decoupled and independently scalable. Kafka also distributes large data streams in real time and replicates data across synchronized broker nodes, so a node failure does not lose data or interrupt operation. Apache Kafka on Heroku is presented as a fully managed service, with multi-tenant basic and single-tenant private plans, automatic broker scaling, and Standard-tier-and-above configurations starting with three brokers and extending to eight. Recommended integration practices include mapping producer-consumer flows, using transactions, topic and schema management, and delivery guarantees, plus monitoring performance and logging Kafka operations.

## Context

Applications receive continuous real-time data from user activity, e-commerce actions, wearable technology, and IoT sensors. The post presents event-driven architecture as a response to the scalability, development-cycle, and maintenance problems associated with tightly coupled monolithic applications.

## Approach / What changed

The post describes using Apache Kafka as the event-centered communication layer for decoupled producers and consumers, then using Apache Kafka on Heroku as a fully managed service. It also recommends defining data flows, applying Kafka’s consistency and delivery features, and monitoring performance and operations.

## Takeaways

- Kafka lets producers publish events to topics while consumers read them independently, allowing components to be updated, tested, and scaled without affecting the entire system.
- Kafka replicates data across synchronized broker nodes, allowing the system to continue operating without data loss when a node fails.
- Apache Kafka on Heroku provides automatic broker scaling, with Standard-tier-and-above plans starting at three brokers and extending to as many as eight.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [Heroku](https://yomu.fyi/topic/heroku), [Kafka](https://yomu.fyi/topic/kafka)

- Source: [Heroku](https://www.heroku.com/blog/building-event-driven-architecture-managed-data-services)
- Source URL: https://www.heroku.com/blog/building-event-driven-architecture-managed-data-services
- Ingested by Yomu: 2026-09-10T00:03:41.001Z

[Read original post](https://www.heroku.com/blog/building-event-driven-architecture-managed-data-services)