What is this Serverless thing?

Why Serverless?

Not just Lambda (FaaS)

Lambda Triggers

Power and Flexibility to build...

Microservices

Microservices work well when:

• Are split into clear Services
• Can be deployed independently
• Only communicate with each other asynchronously
• Master their own data

This is nothing new...

• The Service-Oriented Architecture (SOA) movement, that preceded Microservices, had many of the same tenants

The ESB

The ESB

• Enterprise: Implies use in large Enterprise organisation as often used to tackle complexity in these domains along with the historically large infrastructure investment needed.
   

The ESB

• Service: As this is providing a way for the different Services (logical self-contained representations of business processes) to communicate.
   

The ESB

• Bus: Referencing the hardware element of computers that allows the transfer of signals between different components.

The Event

• Event: “A significant change in state” — K. Mani Chandy

Enter EventBridge

Amazon EventBridge: "Serverless event bus that connects application data from your own apps, SaaS, and AWS services​" -AWS

Enter EventBridge

The biggest Serverless announcement since the release of AWS Lambda.

The key component to building state-of-the-art Serverless EDAs.

Enter EventBridge

The ESB is dead, long live the ESB

• The difference is it's completely Serverless, with no management required.
• Simple integration with existing AWS Services

"Avoiding the Lambda Pinball"

How do I start?

🤷‍♂️

Domain-Driven Design and Event Storming

• Event Storming, an extension to DDD, from Alberto Brandolini is a workshop based approach to discover your domain Events, Boundaries and Entities (or Aggregates)

EventBridge Storming

EventBridge Storming: "A specific variant of EventStorming that reduces rework and tight-coupling for teams building state-of-the-art Serverless Event-Driven Architectures with EventBridge."

EventBridge Storming

1. Event Discovery

2. Temporal Sequencing

4. Categorize into Entities (& Aggregates)

5. Categorization into Bounded Contexts

A Lambda does not a Microservice Make

6. Name Microservices

• One Bounded Context may have multiple Microservices corresponding to its underlying Aggregates & Entities

6. Name Microservices

• ⚠️If an Entity or Aggregate appears in two Bounded Contexts, this implies there should be two independent Microservices to handle the divergent business processes in these two contexts.

7. Creating a Single EventBridge Event Bus

8. Building a Shared Schema

• Teams should be able to work on and deploy Services independently.
• Teams need to agree on the structure of Events, their Schema.
• Title, structure and types.
• Teams should share Schema, not data and code.

EventBridge Schema Registry

EventBridge Storming

EventBridge Storming: "A specific variant of EventStorming that reduces rework and tight-coupling for teams building state-of-the-art Serverless Event-Driven Architectures with EventBridge."

EventBridge Storming

How to trigger an Event?

🤷‍♂️