Florian Lenz

Autonomous microservices with event-driven architecture

Is your microservice architecture just a fragile, distributed monolith? Discover how event-driven patterns create truly autonomous and resilient systems.

Autonomous microservices with event-driven architecture
#1about 2 minutes

Understanding request-driven architecture and service orchestration

Request-driven architecture uses synchronous communication where an orchestrator service manages the flow between other services.

#2about 2 minutes

Decoupling services with an event broker

Event-driven architecture uses an event broker to decouple services, allowing them to communicate asynchronously through events.

#3about 3 minutes

Weighing the pros and cons of event-driven systems

Event-driven systems offer resilience and plug-and-play functionality but introduce challenges like unclear process flows and complex debugging.

#4about 3 minutes

Using the event notification pattern for consistency

The event notification pattern sends a minimal event with just an ID, requiring consumers to make a callback for more data, which favors consistency over availability.

#5about 3 minutes

Achieving autonomy with event-carried state transfer

The event-carried state transfer pattern includes all necessary data within the event itself, eliminating callbacks and promoting service autonomy and availability.

#6about 4 minutes

Storing event history with an event store

An event store captures the complete history of all events, enabling advanced analytics and answering questions that current-state databases cannot.

#7about 4 minutes

Rebuilding system state with event sourcing

Event sourcing uses the event store as the single source of truth, allowing systems to be rebuilt or migrated by replaying events from the beginning.

#8about 1 minute

Defining the core traits of autonomous microservices

An autonomous microservice is highly independent, prioritizes availability over consistency, and uses events for communication to achieve resilience.

#9about 1 minute

Prioritizing business requirements over technical trends

The primary goal is to deliver business value efficiently, which means choosing the simplest architecture that works, even if it's request-driven.

Related jobs
Jobs that call for the skills explored in this talk.

Matching moments

How to build structure and culture without killing agility
05:12 MIN

How to build structure and culture without killing agility

From Data Keeper to Culture Shaper: The Evolution of HR Across Growth Stages

Organizing a developer conference for 15,000 attendees
01:32 MIN

Organizing a developer conference for 15,000 attendees

Cat Herding with Lions and Tigers - Christian Heilmann

Balancing the trade-off between efficiency and resilience
03:38 MIN

Balancing the trade-off between efficiency and resilience

What 2025 Taught Us: A Year-End Special with Hung Lee

Selecting strategic partners and essential event tools
03:17 MIN

Selecting strategic partners and essential event tools

Cat Herding with Lions and Tigers - Christian Heilmann

Why you might not need JavaScript for everything
02:33 MIN

Why you might not need JavaScript for everything

WeAreDevelopers LIVE – You Don’t Need JavaScript, Modern CSS and More

The trend of browsers depending on online services
06:23 MIN

The trend of browsers depending on online services

Developer Time Is Valuable - Use the Right Tools - Kilian Valkhof

Crypto crime, EU regulation, and working while you sleep
01:15 MIN

Crypto crime, EU regulation, and working while you sleep

Fake or News: Self-Driving Cars on Subscription, Crypto Attacks Rising and Working While You Sleep - Théodore Lefèvre

Europe's push for digital independence from US tech
05:17 MIN

Europe's push for digital independence from US tech

WeAreDevelopers LIVE – AI, Freelancing, Keeping Up with Tech and More

Featured Partners

Related Videos

See all videos
The Rise of Reactive Microservices46:24

The Rise of Reactive Microservices

David Leitner

Microservices? Monoliths? An Annoying Discussion!25:05

Microservices? Monoliths? An Annoying Discussion!

Eberhard Wolff

CQRS and Event Sourcing without the pixie dust43:27

CQRS and Event Sourcing without the pixie dust

Allard Buijze

Event-Driven Architecture: Breaking Conversational Barriers with Distributed AI Agents22:19

Event-Driven Architecture: Breaking Conversational Barriers with Distributed AI Agents

Abhimanyu Selvan

Multiple Ships to the Island - Micro Frontends & Island Architectures59:03

Multiple Ships to the Island - Micro Frontends & Island Architectures

Florian Rappl

Durable Execution: A Revolutionary Abstraction for Building Resilient Applications26:08

Durable Execution: A Revolutionary Abstraction for Building Resilient Applications

Maxim Fateev

It’s all about the domain, honey ! Experiences from 15 years of Domain-Driven Design43:13

It’s all about the domain, honey ! Experiences from 15 years of Domain-Driven Design

Carola Lilienthal

Is your backend a hodgepodge of queues, event stores and cron jobs? Durable Execution to the Rescue.29:32

Is your backend a hodgepodge of queues, event stores and cron jobs? Durable Execution to the Rescue.

Maxim Fateev

Related Articles

View all articles
BB
Benedikt Bischof
Why You Shouldn’t Build a Microservice Architecture
Welcome to this issue of the WeAreDevelopers Live Talk series. This article recaps an interesting talk by Michael Eisenbart who talks about the pros and cons of microservice architecture.‍About the speaker:‍Michael has been working for Bosch as a sof...
Why You Shouldn’t Build a Microservice Architecture

From learning to earning

Jobs that call for the skills explored in this talk.