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.

Featured Partners

From learning to earning

Jobs that call for the skills explored in this talk.

Lead Full-Stack Engineer

Lead Full-Stack Engineer

Hubert Burda Media
München, Germany

80-95K
Intermediate
Senior
React
Vue.js
Node.js
MongoDB
+1