---
title: "Event-Driven Architecture — Definition & Engineering Context"
description: "Event-Driven Architecture is a software architecture pattern where database changes, transactions, and user events trigger background services asynchronously via message brokers."
canonical: https://erpstack.io/glossary/event-driven
markdown_url: https://erpstack.io/glossary/event-driven.md
publisher: ERPStack
---

# Event-Driven Architecture

> **Definition:** Event-Driven Architecture is a software architecture pattern where database changes, transactions, and user events trigger background services asynchronously via message brokers.

## In depth

In an event-driven setup, applications do not wait for background tasks (e.g., sending notification emails, updating analytics logs) to finish. The system publishes an event (e.g., 'Order Placed') to a queue, and background workers process it, keeping user response times low.

## How ERPStack applies this

We design event-driven backends using AWS SQS or Redis queues, ensuring that heavy operations do not slow down user interfaces.

## Related reading

- [Apache Kafka](https://erpstack.io/glossary/kafka)
- [Microservices Architecture](https://erpstack.io/glossary/microservices)