Downloaded 39 times
Uploaded byYoav Avrahami
Scaling wix to over 50 m users
The document outlines the growth and scaling challenges faced by Wix from its founding in 2006 to reaching over 50 million users by 2014. It discusses architectural decisions, including the use of caching, cloud hosting, and a move towards micro-services to improve development velocity and product stability. Key strategies such as CI/CD, TDD, and DevOps are emphasized to address fears of change and enhance the company's ability to innovate efficiently.
More Related Content
Similar to Scaling wix to over 50 m users
Scaling wix to over 50 m users
- 1. Scaling Wix toover 50M users
- 5. 2006 2007 20082009 2010 2011 2012 2013 2014 Wix is founded First funding Open beta 1 M users eCommerce 10 M users IPO 50 M users Mobile App Market Hive Wix Worldwide HTML 5
- 6.
- 7.
- 8.
- 9. Cache • You don’tneed a cache • Really, you don`t • Cache is not part of your architecture – Introduce it to solve a problem
- 10. First Challenge -2008 • Server updates imposed downtime • Two concerns • Creating websites • Viewing websites • Different service level needed
- 11. Public vs Editor PublicPublic DB Editor Editor DB
- 12. MySQL is betterNoSQL
- 13. Hosting Co-Location Managed HostingCloud Lease hardware and maintenance Overnight provisioning Reliable software and hardware Instant lease hardware Instant provisioning unlimited resources Reliable software unreliable hardware Own and maintain your hardware Provision -> buy deliver and install Reliable software and hardware
- 14. 2006 2011 20122013 2014 Austin Amsterdam Amazon, Google Chicago Tampa
- 15. Wix Media • 500GByte of small files – Hit IO limitations • Need scalable solution – Number of files – HTTP connections • Image manipulations
- 16. Wix Media Platform x36 x36 x32 x36 x36 x32 Austin Chicago get37D815B5.jpg First fallback CDN If not in CDN
- 17. Wix Media Platform x36 x36 x32 x36 x36 x32 Google Cloud Austin Chicago get37D815B5.jpg First fallback Second fallback CDN If not in CDN
- 18. Wix Media Platform Google Cloud Austin Tampa get37D815B5.jpg CDN If not in CDN Amazon Cloud
- 20. CDN • Use aCDN! • Cache killer pattern – http://static.wix.com/client/1.3.2/css/viewer.css
- 21. Development Velocity -2010 • Large and entangled codebase • Hard feature rollout • While at the same time, the iPad was released • We needed to enable Wix to move fast
- 22. 2011 2012 20132014 CI / CD / TDD DevOps ScalaWix Framework Micro-Services 2010 TDD Redux Companies & Guilds
- 23.
- 24.
- 25. Why CI /CD / TDD / DevOps? • Fear of change • Low quality • Slow product development • 3 months from dev to GA I want change I want stability
- 26. CI / CD/ TDD / DevOps • Small and fast changes • Empower the developer • Automate!!! • Measure!!! • = x xRisk Number of changes Size of change $$$ impact of change
- 27.
- 28.
- 29.
- 30. Micro-Services • Over 100micro-services at Wix • Each service is a process • Independent development & deployment • Risk mitigation • Increases % of network failures • Back / Forward compatibility • Size of a service – as large as the team
- 31. Companies & Guilds •Companies focus on products • Guilds focus on technology How What Company leader Guild master
- 32.
Editor's Notes
- #7 Built for fast development Did not know what are business is We know we will need to replace it Did not know how hard that will be
- #10 Cache management – how do you know what is in the cache? How do you find invalid data in the cache? Invalidation – who invalidates the cache? When? Why? Cache Reset – can your architecture stand a cache restart?
- #11 Sites should never ever have a downtime! Sites should work as fast as possible, always! However, an editing system does not require this level of SLA
- #12 Releases of Editing feature should have no impact on existing site operations! Solution - The two concerns evolve independently The Public segment targets serving websites Has mostly read-only usage pattern Simple publishing system Simple + readonly -> simpler to have higher SLA and DRP MySQL used as NoSQL – single large table with XML text fields The Editor segment Exposes the Editing APIs, user account and galleries management. Has different release schedule compared to the Public segment
- #13 Use one non-normalized table, primary key access, json fields Immutable blobs, blog table with pointers No transactions No MySQL auto generated keys GUID for keys – no locks, enable master master replication
- #15 Amsterdam for 3 way active active -> failed Doing 2 way active active + service disruption on third
- #16 The “upload to app server, post process files, copy to lighttpd server, serve by lighttpd” pattern proved inefficient, slow and error prone ls does not scale Needed control over http headers for caching
- #21 CDN acts as a great connection manager - We have CDN hit ratio’s of over 99.9% There are many vendors We started with 1 CDN vendor We are now working with two CDN vendors Different CDN vendors have advantages at different geo Tune HTTP Headers per CDN Vendor CDN Vendors interpret HTTP headers differently
- #24 Train the people you already have Hiring the right people is key to success Hire only the best developers (only seniors) Don’t count only on the interview, you need to test actual coding Hire people who will challenge you (no “yes man”) Get people you can trust with “root” access to production Never stop hiring