8 Lessons Learned from using Kafka with 1000 microservices
summary
Wix runs ~1,500 microservices and 1.5 billion Kafka messages per day and builds a shared Kafka layer called Greyhound rewritten on ZIO. Greyhound adds parallel consumption via fibers, automatic commit and header-based context propagation, built-in retry topics plus a blocking-retry policy and per-service dashboards. Self-service back-office and schema discovery reduce ops load, Prometheus/Grafana metrics trigger alerts on consumer lag, Node.js uses a gRPC sidecar to reuse Java/Scala features, and clusters are proactively trimmed or migrated to Confluent Cloud.
AI-written summary · about
chapters (4)
related talks
52m10 LESSONS LEARNED FROM USING KAFKA IN 1000 SCALA MICROSERVICES
46mLessons Learned From Working with 2000 Event-Driven Microservices
54mLessons learned from working with 2000 event-driven microservices
35mPolyglot, Fault-Tolerant Event-Driven Programming with Kafka....
37mKafka Based Global Data Mesh at Wix
43mBattle-tested event-driven patterns for your Microservices archit.
41mBattle-tested event-driven patterns for your microservices
29mGreyhound - Powerful Pure Functional Kafka library
