David Leitner
The Rise of Reactive Microservices
#1about 3 minutes
The pitfalls of synchronous microservice communication
Synchronous calls between services create tight coupling and lead to cascading failures when downstream systems experience latency.
#2about 4 minutes
Decoupling services with asynchronous message queues
Using message queues like RabbitMQ isolates high-latency services and improves system resilience by changing from immediate creation to eventual acceptance.
#3about 4 minutes
Avoiding the entity service anti-pattern in architecture
Slicing microservices based on data entities like 'user' or 'account' creates dependencies across teams and slows down feature development.
#4about 7 minutes
Using push-based streams for data synchronization
Reactive systems push data changes through event streams, allowing services to build local read models (projections) and achieve runtime autonomy.
#5about 7 minutes
Navigating the challenges of eventual consistency
Eventual consistency involves three main challenges—divergence, variance, and latency—which can be managed with ordering, deduplication, and optimistic UIs.
#6about 5 minutes
The key benefits of building reactive systems
Reactive architectures improve resilience and enable horizontal scaling by creating autonomous services that can build real-time, push-based user interfaces.
#7about 2 minutes
Decomposing monoliths with change data capture
Change Data Capture (CDC) streams events directly from a legacy database's transaction log, enabling gradual monolith decomposition without modifying the legacy code.
#8about 6 minutes
Achieving massive throughput with sharded architectures
Sharding partitions data and processing across independent streams, enabling systems to scale horizontally and handle nearly unlimited throughput.
#9about 3 minutes
Balancing architectural complexity and business needs
Evolving from a monolith to a sharded, stream-based system adds powerful capabilities but also increases complexity, so always choose the simplest architecture that meets your requirements.
#10about 3 minutes
Answering questions on micro-frontends and data ownership
The speaker discusses how micro-frontends align with team autonomy and clarifies that while data can be copied to projections, updates must go through the owning service.
Related jobs
Jobs that call for the skills explored in this talk.
Featured Partners
Related Videos
Rethinking Reactive Architectures with GraphQL
David Leitner
CQRS and Event Sourcing without the pixie dust
Allard Buijze
Is reactive the new black? Imperative vs. reactive programming with Quarkus
Tatiana Chervova
It’s all about the domain, honey ! Experiences from 15 years of Domain-Driven Design
Carola Lilienthal
Building high performance and scalable architectures for enterprises
Luka Samaržija & Ivan Sokol
Micro-frontends anti-patterns
Luca Mezzalira
Kafka Streams Microservices
Denis Washington & Olli Salonen
Microfrontends at Scale
Josh Goldberg
From learning to earning
Jobs that call for the skills explored in this talk.




Senior Fullstack Engineer – Angular/.Net (f/m/d)
Apaleo
München, Germany
Remote
€65-85K
Senior
.NET
Angular
JavaScript
+1


Senior DevOps Engineer (f/m/x)
Douglas GmbH
Düsseldorf, Germany
Senior
Kubernetes
Cloud (AWS/Google/Azure)


Senior Systems/DevOps Developer (f/m/d)
Bonial International GmbH
Berlin, Germany
Senior
Python
Terraform
Kubernetes
Elasticsearch
Amazon Web Services (AWS)


(Senior) IT Cloud Architekt /Banking (all genders)
msg
Ismaning, Germany
Intermediate
Senior
Docker
DevOps
Openshift
Kubernetes


![Senior Software Engineer [TypeScript] (Prisma Postgres)](https://wearedevelopers.imgix.net/company/283ba9dbbab3649de02b9b49e6284fd9/cover/oKWz2s90Z218LE8pFthP.png?w=400&ar=3.55&fit=crop&crop=entropy&auto=compress,format)

Senior Software Engineer [TypeScript] (Prisma Postgres)
Prisma
Remote
Senior
Node.js
TypeScript
PostgreSQL
Software Architect (Contractor) - Composable Commerce & Event-Driven Design
CobbleWeb
Birmingham, United Kingdom
Remote
€61K
Redis
React
Node.js
+4




