Battle-tested event-driven patterns for your microservices

on YouTube ↗41m

" summary

Wix runs ~2,200 microservices and 2.5 billion Kafka messages per day and uses four battle-tested patterns: Consume and Project (reverse-lookup writer + reader materializes a narrow DB view and cuts load on the monolith), End-to-end Events (Kafka + websockets carry job status across DCs for imports), In-memory KV stores (compacted topics loaded to RAM for zero-latency lookups), and Exactly-once/transactions (idempotent producers + Kafka transactions for payment-critical deduplication). These patterns are production-proven and reduce DB contention, enable cross-DC routing, and require memory-sized datasets for KV.

AI-written summary · about

" chapters (10)

1. 0:00Intro
2. 1:00About Wix
3. 1:30Overview
4. 4:27Communication between microservices
5. 12:55Battletested patterns
6. 14:30Consume and project patterns
7. 19:44Eventdriven from end to end
8. 24:40Zero latency key value store
9. 31:27Events in transactions
10. 38:26Wrap up

" related talks

• 43mBattle-tested event-driven patterns for your Microservices archit.Natan Silnitsky · Devoxx Ukraine 2020
• 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
• 37mKafka Based Global Data Mesh at WixNatan Silnitsky · DevDays Europe 2022
• 30m8 Lessons Learned from using Kafka with 1000 microservicesNatan Silnitsky · Scale By the Bay 2020
• 35mPolyglot, Fault-Tolerant Event-Driven Programming with Kafka....Natan Silnitsky · Devoxx Ukraine 2020
• 34mAdvanced Caching Patterns used by 2000 microservicesNatan Silnitsky · Devoxx Ukraine 2021
• 52m10 LESSONS LEARNED FROM USING KAFKA IN 1000 SCALA MICROSERVICESNatan Silnitsky · Scalar 2020