Battle-tested event-driven patterns for your Microservices archit.

on YouTube ↗43m

" summary

Wix runs ~1.5 billion Kafka messages per day across ~1,500 microservices and uses Kafka + websockets to build concrete solutions: a Consume and Project flow that produces site‑updated events and creates a reverse‑lookup writer/reader pair to cut database load, an End-to-end Events pipeline that pushes job status from workers to browsers via websockets, an In memory KV stores layer built on compacted topics for zero‑latency configs, and Events transactions (Kafka exactly‑once/transactions) for critical idempotent payment paths.

AI-written summary · about

" chapters (9)

1. 0:00Introduction and welcome
2. 1:07About the speaker and context
3. 3:39From monolith to microservices
4. 11:09Consume and project pattern
5. 17:57Event-driven end-to-end flow
6. 22:59Zero latency key value store
7. 31:54Events in transactions
8. 40:08Key takeaways and resources
9. 42:16Q&A session

" related talks

• 41mBattle-tested event-driven patterns for your microservicesNatan Silnitsky · Scale By the Bay 2021
• 46mLessons Learned From Working with 2000 Event-Driven MicroservicesNatan Silnitsky · Build Stuff 2022
• 54mLessons learned from working with 2000 event-driven microservicesNatan Silnitsky · GeeCON 2023
• 30m8 Lessons Learned from using Kafka with 1000 microservicesNatan Silnitsky · Scale By the Bay 2020
• 37mKafka Based Global Data Mesh at WixNatan Silnitsky · DevDays Europe 2022
• 52m10 LESSONS LEARNED FROM USING KAFKA IN 1000 SCALA MICROSERVICESNatan Silnitsky · Scalar 2020
• 34mAdvanced Caching Patterns used by 2000 microservicesNatan Silnitsky · Devoxx Ukraine 2021
• 45mBuilding Event-Driven Microservices with Event Sourcing and CQRSLidan Hifi · NDC Oslo 2018