Retrospective: The Magento Commerce Cloud at Work

Transcription

1

2 Retrospective: The Magento Commerce Cloud at Work

3 Jon Tudhope Director Interactive Development Something

4 Agenda Why Commerce Cloud A Typical implementation Commerce Cloud enables merchant growth Commerce Cloud enables SI growth

5 The Conversation Why did my product description not update on the front end? Can I run my site on a single web server to save costs? How likely is it my site will go down during an event? How much downtime will I have this year? The site seems slow is it just me? Why do I have intermittent outages?

6 Better things to keep you up at night What is my average customer lifetime value Are my best customers at saturation with the mail marketing campaigns I should be coordinating social, , and onsite marketing How do I engage a younger demographic How do I improve my repeat customer engagement in the first 90 days

7 Why cloud? Redundancy Automatable Scalable Flexible Captain Scruffington SRF001-SRF100

8 Planning capacity 7000 Transactions per day Baseline Infrastructure - Peak Baseline Infrastructure Average + Seasonal 0 1/1/17 2/1/17 3/1/17 4/1/17 5/1/17 6/1/17 7/1/17 8/1/17 9/1/17 10/1/17 11/1/17 12/1/17

9 Engineering the cloud Deployment to a cluster Failover Shared storage Access control Logs Scaling Patching

10 New Code to support

11 Why Commerce Cloud Cloud management process & tooling

12 Why Commerce Cloud Includes important tools BI, New Relic, Fastly, Black Fire

13 Why Commerce Cloud Cost competitive

14 Case Study: Cost Comparison ECE Managed Hosting 4K Page views / hour (Peak) 20K Visits Traffic 500 Orders per month AOV $100 3 Store Views Hosting AWS Managed Hosting Magento BI Included $$ Devops / Sysops Included Included Fastly Included $$ Database replication Yes No Web cluster / load balance Yes Yes DC Redundancy Yes No Magento License Included $$ PCI Hosting Configuration 3 Webs 3 Dbs 3 Elastic Search 2 Webs 1 DBs (Elastic Search, REDIS, NFS) Black Fire Included $$ New Relic Included $$ Hosting / Fees $$ $$ Total $X $X + 30%

15 Why Commerce Cloud Developer portability Well documented Standardized Infrastructure code owned by infrastructure service provider

16 Why Commerce Cloud Good practices

17 Reference: Stack

18 Did Commerce Cloud deliver Hosting related issues significantly reduced No capacity related downtime to date Infrastructure conversations in strategic conversations reduced / eliminated Greater confidence to execute on marketing campaigns We still discuss caching and indexing Commerce cloud has evolved since the initial implementation SD focused little time and effort on infrastructure automation

19 Reference Implementation

20 Team Structure Launch Manager Application Support Team Infrastructure Support Team L2 Application Escalation Team

21 Things to know Read-only file system Build is process prescriptive Integration vs Production / Staging Wordpress & third party apps Patching Platform CLI Not really cattle Separate repo for browsing magento-vars file

22 Areas for Improvement Multi-site build server disk space Opaque build routines IonCube & Blackfire SSH Keys Shifting tooling and protocol landscape Still maturing Scaling is vertical Limited infrastructure alerting Ghost Commits

23 The Good Quick uptime & start time High availability Multiple environments Transparency for client Standardized code management pipeline Universal infrastructure Log rotation

24 ECE Enables Merchant Growth

25 Enabling merchant growth Flexible scaling Cost effective Redundant Infrastructure and application benchmarks High Availability Our experience % to date across tracked sites As reported through Pingdom uptime monitoring for unplanned outages Business Intelligence reporting Parallel development streams

26 Transparency Application Insight Customer & Business Insight Development Activity

27 Unified Front Application support engages infrastructure support directly SI coordinates communication between groups as needed

28 Holiday / High Traffic Periods Submit ticket to increase server capacity 48 hours in advance 45 days overage/higher server capacity per year with cloud agreement Upsize requests must be made in 5 day increments Team offer to upsize as necessary and notify via a support ticket. Changing server configuration / size does not require any site downtime.

29 Enabling Partners

30 Partner Enablement Focus on core competencies Quick to start Consistent toolbox Transition

31 The SI Equation IF [Return on Investment] > [Investment on ecommerce Platform] Then [Investment]++

32 Promise delivered? Revenue generating initiatives Core strengths Availability Manage risk Cost competitive Transparency

33