Intro Eda Ent
Intro Eda Ent
to event-driven
architectures
I N T R O D U C T IO N
Events are everywhere: A customer places an item in a shopping cart. A financial document is
submitted. A new user creates an account. A healthcare dataset is uploaded. In an event-driven
architecture (EDA), events are the center of an application, powering communication between
integrated systems. Building event-driven architectures is driving innovation across industries,
with organizations like Taco Bell, Bosch Thermotechnology, and Nationwide Children’s
Hospital. Event-driven architectures can help you accelerate modernization, reduce total cost
of ownership (TCO), and build better products faster.
The diagram on the next page depicts a typical event-driven architecture, which comprises
event producers, event brokers, and event consumers. Business events like placing an order
or submitting a return are created by event producers. An event broker receives those events
and sends them on to the event consumers. Event consumers need to take action on the events.
They include backend systems, warehouse management, finance, and customer relations.
2
Figure 1: Example of an event-driven architecture
New order
With events, customers can create loosely coupled, fault-tolerant integrations between
microservices, software-as-a-service (SaaS) applications, and applications running on premises
and in the cloud. Building with asynchronous events gives development teams the ability
to build and deploy independently, enabling them to launch features faster and deliver
better customer experiences. Event-driven architectures enable businesses to unlock agility,
extensibility, and real-time business insights.
3
Why organizations are
adopting EDAs to build
modern applications
4
3. Event-driven architectures provide real-time, actionable
insights, creating better experiences for your customers.
Organizations are looking for ways to unlock the value of events and
data in their applications. They want to build dynamic, high-quality
experiences and use artificial intelligence (AI)- and machine learning
(ML)-powered personalization to better engage their end users. They
also want to extract valuable insights from their events that are
actionable today rather than waiting for a weekly or monthly report
cycle. Event-driven architectures allow customers to ingest, process,
and react to events in real time.
5
Building event-driven
architectures on AWS
Amazon Web Services (AWS) makes it easier to build event-driven architectures by offering a
comprehensive set of serverless services that gives organizations the ability to select the right
tool to fit their business requirements and reduce the amount of integration code needed.
With serverless and managed integration services, customers can take advantage of
built-in functionality and infrastructure management, allowing them to build faster and
maintain less.
Organizations can integrate across a portfolio of over 200 AWS services and more than 45
natively integrated SaaS partners. Where organizations building event-driven architectures
would previously need to do the heavy lifting of writing code for emitting, ingesting, and
processing events themselves, on AWS, over 80 services emit events by default, making
EDAs a natural fit. One example is Amazon Simple Storage Service (Amazon S3), which
sends over 125 billion event notifications to serverless applications each day.
AWS continues to invest and innovate in services that help organizations build event-
driven architectures, transform application development, and accelerate their innovation.
6
C O N C L U SIO N
AWS makes it easier for organizations to build event-driven architectures with the most
comprehensive set of serverless services, pre-built integrations, and continuous innovation.
Transform your application development, accelerate innovation, and save costs with an event-
driven architecture built on AWS.
©️ 2023, Amazon Web Services, Inc. or its affiliates. All rights reserved. 7