Lightning Talk: Event Based Communication in Complex Micro-service...

on YouTube ↗11m

" summary

Starts from a monolith, migrates to microservices, then replaces synchronous request/response with an event stream to avoid cascading failures and manual compensating logic. Implementation uses Apache Kafka as the durable event log, services produce transactional events and consumers replay missed messages when a downstream service is down, and a WebSocket service pushes final UI state so users see reactive order success without polling. Result: scalable, loosely coupled ordering pipeline that handles outages without lost events.

AI-written summary · about

" chapters (5)

1. 0:00Introduction
2. 0:25Agenda
3. 0:55monolithic architecture
4. 3:06microservices
5. 5:41eventbased communication

" related talks

• 37mBeyond Microservices: Streams, State & ScalabilityGwen Shapira · GOTO Chicago 2020
• 47mThe Rise of Reactive MicroservicesDavid Leitner · Craft Conference 2022
• 47mEvent-Driven Microservices = Microservices Done RightUrs Peter · J-Fall 2022
• 42mCreating event-driven microservices: the why, how and whatKatherine Stanley · Voxxed Days Microservices 2019
• 24mPatterns of Evolution from Monolith to MicroservicesKarina Mora · HashiTalks 2022
• 01h 03mMicroservices vs The Distributed MonolithChris Riley · PHP UK Conference 2024
• 54mRethinking REST in a Microservices WorldJames Roper · Philly ETE 2016
• 58mImplementing Event-driven MicroservicesNikhil Barthwal · DevOpsCon Spring 2019