Building Event-driven Architectures with Amazon EventBridge

© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
James Beswick, AWS Serverless
@jbesw
April 22, 2020
Event driven architectures with
Amazon EventBridge
© 2020, Amazon Web Services, inc. or its Affiliates. All rights reserved.

About me
• James Beswick
• Email: jbeswick@amazon.com
• Twitter: @jbesw
• Senior Developer Advocate – AWS Serverless
• Serverless geek
• Software developer and PM activist
• Previously:
• Multiple start-up tech guy
• Rackspace, USAA, Morgan Stanley, J P Morgan…
• AWS customer since 2012

Agenda
Amazon EventBridge
Common Use cases
Event driven architectures

© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Monoliths are everywhere

Monoliths and microservices
Monolith
Does everything
Microservices
Does one thing

The end goal
Reliability
Resilience
Customer value
Scalability
And do it faster

Challenges with distributed systems

Coupling

😐
A simple example – the synchronous API
Client
POST
/order
201 201
POST
/invoice
😀

Decoupled – no monolith

More services get added over time…

V2, v3, v5, v8….

Wait! This looks like a monolith…
What does failure recovery look like for
this?

Choreographing APIs is hard

The happy path of API workflow

Wait! We’re out of stock.

Wait! There’s another service?

Availability with synchronous APIs

Availability with synchronous APIs
Payment
Order
service

How can events help with these 3 challenges?

event
[i-’vent] noun
A signal that a system’s
state has changed.

Events are asynchronous
Synchronous
Commands
Client Service A Service B
Asynchronous
Events
Client Service A Service B

Events are observable, not directed
Directed Commands Observable Events

How do we change this implementation?
An order was created!

Event bus
Abstracts producers
and consumers
Selects and filters
events

Event buses for coordination
Event bus

Decoupling with the event bus
Event bus

Events with Amazon EventBridge
Order
service
• Your services can both
produce messages onto
the bus and consume
just the messages they
need from the bus
• Services don’t need to
know about each other,
just about the bus.
Event bus

How do you expand beyond your own
systems?

Getting data from other systems
Your environmentSaaS provider
? Your
service

Option 1: Polling
Your
service
Poller function

Option 2: Webhooks
Your
service
http endpoint
authorizer

Advantages
Simple POST/GET request
More efficient than polling
Near real-time
Webhooks
Disadvantages
Lost info if your service is down
Limited security options
More infrastructure to manage
Public http endpoint
Uses public Internet
Difficult to scale

Can we do better than webhooks?

Amazon
EventBridge
A serverless event bus service
for SaaS and AWS services

What is serverless?
No infrastructure provisioning,
no management
Automatic scaling
Pay for value Highly available and secure

© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2020, Amazon Web Services, inc. or its Affiliates. All rights reserved.
Event-driven compute
Functions as a service
Serverless FaaS

Serverless Applications
Event source Services
(anything)
Changes in
data state
Requests to
endpoints
Changes in
Resource state
Function
Node.js
Python
Java
Go
Ruby
.Net (C#/Powershell)
Custom Runtime API

Lambda execution model
Synchronous
(push)
Asynchronous
(event)
Stream
(Poll-based)
Amazon
DynamoDB
Amazon
SNS
/order
Amazon
S3
reqs
Amazon
Kinesis
changes
AWS Lambda
service
Amazon API
Gateway
Lambda
function
Lambda
function
function

• Fully managed, pay-as-you-go
• Native integration with SaaS
providers
• 90+ AWS services as sources
• 17 AWS services as targets
• $1 per million events put into
the bus
• No additional cost for delivery
Amazon
EventBridge
A serverless event bus service
for SaaS and AWS services

Amazon EventBridge
Event source SaaS event bus
Custom event bus
Default event bus
Rules
AWS Lambda
Amazon Kinesis
AWS Step Functions
Additional targets

Amazon EventBridge
Custom event bus
Default event bus
Rules
Event sources
AWS Lambda
Amazon Kinesis
AWS Step Functions
Additional targets

Amazon EventBridge
Custom event bus
Default event bus
Rules
AWS Lambda
Amazon Kinesis
AWS Step Functions
Additional targets
Event
buses

Amazon EventBridge
AWS services
Custom events
SaaS apps Event source SaaS event bus
Custom event bus
Default event bus
Rules
Example event:
{
"detail-type": "Ticket Created",
"source": "aws.partner/example.com/123",
"detail": {
"ticketId": ”987654321",
"department": "billing",
"creator": "user12345"
...
}
}
AWS Lambda
Amazon Kinesis
AWS Step Functions
Additional targets

Amazon EventBridge
AWS services
Custom events
Custom event bus
Default event bus
Rules
AWS Lambda
Amazon Kinesis
AWS Step Functions
Additional targets
Example event:
{
"detail": {
"ticketId": ”987654321",
...
}
}
Example rule:
{
"source": ["aws.partner/example.com/123"]
}

Amazon EventBridge
AWS services
Custom events
Custom event bus
Default event bus
Rules
AWS Lambda
Amazon Kinesis
AWS Step Functions
Additional targets
Example event:
{
"detail": {
"ticketId": ”987654321",
...
}
}
Example rule:
{
"detail": {
"department": ["billing", "fulfillment"]
}
}

Amazon EventBridge
AWS services
Custom events
Custom event bus
Default event bus
Rules
AWS Lambda
Amazon Kinesis
AWS Step Functions
Additional targets
Example event:
{
"detail": {
"ticketId": ”987654321",
...
}
}
Example rule:
{
"detail-type": ["Ticket Resolved"]
}

Amazon EventBridge
AWS services
Custom events
Custom event bus
Default event bus
Rules
AWS Lambda
Amazon Kinesis
AWS Step Functions
Additional targets
Targets

Show me the code

The original example

The original example… with an event bus
Event bus
Routing/filtering
rules

Routing/filtering
rules
Event bus
Routing/filtering
rules

… and what about the Rewards service?

Routing/filtering
rules
Event bus

Amazon
EventBridge
• Source of truth for sharing
schema
• Explicitly published and auto-
discovered
• Integrations for VS Code and
JetBrains
• Language bindings for Java,
Python, and TypeScript
Schema registry

Common EventBridge use cases
Take action
AWS LambdaAmazon EventBridge
Applications and
resources
AWS Service
Run workflows
AWS Step FunctionsAmazon EventBridgeApplication Event
Apply intelligence Amazon Comprehend
Amazon SageMaker
AWS LambdaAmazon EventBridgeSaaS application

Common EventBridge use cases
Audit and analyze
Amazon EventBridgeApplication Event Amazon Kinesis
Data Firehose
Amazon S3 Amazon Athena
Synchronize data
Amazon EventBridgeSaaS application Amazon DynamoDBAWS Lambda
fetch

Your account - 111111111111
SaaS partner account
Partner event
source
AWS Lambda
Amazon Simple
Queue Service
1. Register your AWS account
ID with SaaS partner
AWS account ID
111111111111
AWS Region
us-east-1
Onboarding a SaaS event source with EventBridge

Partner event
source
2. Associate the event source
with an event bus
Event bus
Your account - 111111111111
AWS Lambda
Amazon Simple
Queue Service

3. Configure rules and targets Your account - 111111111111
Partner event
source
AWS Lambda
Amazon Simple
Queue Service
Event bus
rule
rule

Demo

Amazon
EventBridge
Order
service

Amazon
EventBridge
Order
service
• Your services can both
produce messages onto
the bus and consume
just the messages they
need from the bus
• Services don’t need to
know about each other,
just about the bus.

Conclusion
Decoupling Simplified event
routing
Improved
availability
Third party
integration

Thank you!
James Beswick
Developer Advocate, AWS Serverless
jbeswick@amazon.com
@jbesw

Building Event-driven Architectures with Amazon EventBridge

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Building Event-driven Architectures with Amazon EventBridge

Similar to Building Event-driven Architectures with Amazon EventBridge (20)

More from James Beswick

More from James Beswick (6)

Recently uploaded

Recently uploaded (20)

Building Event-driven Architectures with Amazon EventBridge