Simple Helix Presentation | The 2nd Annual eCommerce Expo South Florida
Download as PPTX, PDF0 likes185 views
1. The document discusses planning for variable traffic on a Magento site by moving to a stateless architecture that allows horizontal and vertical scaling. 2. A stateless design keeps no local session or state records, allowing unlimited scaling of nodes and centralized data storage. 3. The summary outlines how to expand a Magento cluster from a single server to a stateless configuration with load balancing, separate databases, caching, and media servers for scalability.
Simple Helix Presentation | The 2nd Annual eCommerce Expo South Florida
- 1. For Rapid TrafficFluctuation SimpleHelix Presents
- 2. STANDARD MAGENTO ENVIRONMENT Singlepoint of failurethat is difficult to scale Single-server instancehousing both web filesand site database Cacheand sessionsstored on thefile-system
- 3. PLANNINGFORTRAFFICSPIKES 01 02 03 04 05 Build resourcebaselinefrom averagetraffic levels Plan for 10-20%moretraffic than expected Determineif horizontal or vertical expansion isrequired Bring resourcesonlineand perform stress-testing Processistimeconsumingand can beexpensive
- 4. IncreaseCPU/RAM resourceson server Split web and database servicesacrosstwo servers VERTICAL EXPANSION OPTIONS
- 5. Load balancer distributestraffic evenly acrossall nodes Deploy additional web server nodes HORIZONTAL EXPANSION OPTIONS
- 6. No centralized filestoragefor /media or /var Admin Dashboard errorsmay occur duringuploads/imports Session data must bestored in databaseaddingoverhead Expansion can beexpensive, timeconsuming, and will requiredowntime PROBLEMSWITH EXPANSION 01 02 03 04
- 8. Sales, media campaigns, social media trends, etc UNEXPECTED TRAFFIC SPIKES Without planning can lead to server overload and lost sales
- 10. AStatelesssystem keepsno local state/session record SCALABILITYREQUIRESASTATELESS ENVIRONMENT 01 02 03 04 Thevalueof output(s) at any point in timedependsonly on the valueof input(s) Allowsfor a virtuallyunlimited number of new node creations Data dependingon a specific statemust becentralized for nodeaccess
- 11. Providesability to scaleresourcesvertically and horizontally Minimizeor eliminatedowntime Improveperformance Improvesecurity Takeadvantageof load balancing, auto scaling, etc. UTILIZESTATELESSDESIGN FROMDAY1 01 02 03 04 05
- 12. DNSA-record TTLset low to enablefast propagation (or utilizeserviceslikeCloudFlare) Session storagein Memcache/Redis Cachestoragein Redis CDNfor Media accessand distribution Databaseconfigured with binary logging for easy replication Configuration management (Puppet / Chef / Salt / etc) CONSIDERATIONSFORSTATELESSDESIGN 01 02 03 04 05 06
- 13. MAGENTOCLUSTEREXPANSION Initial Magento deployment on single-server environment Session and Cachedata stored on separateRedis daemons NFSexport created for media and var directories Binary logging enabled for databaseservice Configurationsstoresin automation system such as Chef / Puppet / Salt
- 14. MAGENTOCLUSTEREXPANSION Databaseserver config pushed from automation system Binary logging used to createa databaseslaveon separateserver Databaseslavepromoted to master to complete databasemigration
- 15. MAGENTOCLUSTEREXPANSION Push Redis/SOLRconfiguration from automation system to new servers MoveSession / Cache/ Search daemonsto individual instances
- 16. MAGENTOCLUSTEREXPANSION Utilizelow DNSA-record TTLto add a load balancer edgedevice Web Server #1pullsmedia and var NFSmountsfrom admin server Cache/ Session / Search pulled from centralized daemons
- 18. SUMMARY 01 02 03 Usea statelessdesign model from Day 1 Scaleinfrastructureto meet traffic demands 04 MaximizeROI Avoid wastingresourcesand only pay for what you need