Scaling Horizons Effective Strategies for Wix's Scaling challenges

on YouTube ↗44m

" summary

Wix runs ~4,000 microservices and handles 3.5 billion daily HTTP transactions and 70 billion Kafka messages, so scaling choices are concrete: deploy per-Kafka-cluster consumer proxy fleets to cut managed-Kafka cost and avoid single points, split web traffic into editor vs public segments at the load balancer, use QoS fleets (three groups) for noisy webhook tenants, choose DynamoDB for auto-sharding while respecting its limits (DynamoDB partitions: 10 GB / 3k RCU / 1k WCU), and use ProxySQL query hints for geo routing to support MySQL geo-shards — horizontal scaling reduces single-node limits but increases operational complexity.

AI-written summary · about

" chapters (9)

1. 0:00Introduction and speaker intro
2. 3:18Vertical vs horizontal scaling
3. 8:18Fixed routing strategies
4. 17:15Wix web traffic segmentation
5. 20:08Dynamic routing for reactions app
6. 28:57Data sharding with DynamoDB
7. 31:53Geo-based data locality for enterprises
8. 34:42Key takeaways and scaling summary
9. 40:46Q&A session

" related talks

• 51mScaling Wix with microservices architectureAviran Mordo · JavaDay Kyiv 2015
• 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
• 41mBattle-tested event-driven patterns for your microservicesNatan Silnitsky · Scale By the Bay 2021
• 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
• 43mBattle-tested event-driven patterns for your Microservices archit.Natan Silnitsky · Devoxx Ukraine 2020
• 36mThe Art of Decomposing MonolithsKfir Bloch · Codemotion Amsterdam 2016