to be or not to be in the cloud - imagine.magento.com success ii... · • provides testing...
TRANSCRIPT
Where every interaction matters.
To Be or Not to Be in the CloudPresented by:
Frank DiRoccoProduct Manager
Objectives
▪ Is “The Cloud” for me?▪ Characteristics of Cloud & Physical Environments▪ Comparing Transaction Volumes▪ Business Objective Considerations▪ Use-cases for Cloud & Physical Environments▪ Conclusion and Questions
2Where every interaction matters.
30
Introductions▪ From Peer 1 Hosting:
- Frank DiRoccoProduct Manager
3Where every interaction matters.
Is “The Cloud” for me?• Designing a Magento Platform on both Cloud
and Physical Solutions
• Do merchant needs vary from one solution to another?
• How do Cloud Solutions compare to Physical Solutions:
• Ease of Deployment and Sustainment• Transaction Volume vs. Complexity
4Where every interaction matters.
Where every interaction matters.
Characteristics ofCloud & Physical Environments
Cloud Environments• Subdivided physical hosts into one or more
independent virtual hosts or applications
• Highly portable and extremely agile in adding, removing or moving resources
• Shared resources pose risk of “noisy neighbors” and privacy concerns around compliance
• Utility billing models and lack of contract are appealing for development and short-term projects
6Where every interaction matters.
Physical Environments• Physical proximity of hosts is ensured
• Ensures all available resources can be focused on your business objectives
• Capital Expenditures can be annualized by hosting contracts
• Provisioning and hardware modification is slow
• Modifications require scheduling and potentially down-time or fail-over
7Where every interaction matters.
Where every interaction matters.
Comparing Transaction Volumes
Magento Performance Toolkit• Standardizes Magento platform and
store benchmarking
• Focuses on dynamic requests to the application
• Divides application requests among typical store functionality
• Provides testing profiles to baseline a Magento platform for performance
9Where every interaction matters.
30%
4%
4%
62%
Just BrowsingBrowse, Add, Guest CheckoutBrowse, Add, User CheckoutBrowse, Add, Abandon
Cloud Testing Environment
10Where every interaction matters.
Physical Testing Environment
11Where every interaction matters.
Magento 1.14 Performance
12
262 453 479 518 613 619
383
707
822
693 702
819
0100200300400500600700800900
Response Time (ms) Avg. Resp. Time
Std. Dev. Resp. Time
Where every interaction matters.
21.5 21.4
31.5
52.3 51.8
72.7
0
10
20
30
40
50
60
70
80
Transactions Throughput(tx/sec)
Where every interaction matters.
Business Objective Considerations
Business Objectives• Use the minimal solution necessary to deliver
the transactional volume required
• Understand just how agile your ecommerce solution needs to be
• Reduce complexity where possible
• Ensure ample time to scale horizontally
14Where every interaction matters.
Where every interaction matters.
Use-Cases forCloud & Physical Environments
Typical Cloud Use-Cases• Need to add/remove and adjust server
resources regularly and without delay
• Need to leverage short-term billing models for projects lasting less than 6 months
• Short-term seasonal traffic spikes
• Unknown and difficult to estimate traffic fluctuations
16Where every interaction matters.
Typical Physical Use-Cases• Need for high transaction volume without added
complexity
• Predictable traffic patterns resulting from mass-marketing events
• Long-term seasonal traffic spikes
• Long-term billing models for +1 year projects
17Where every interaction matters.
Conclusion• Magento Platform is indeed needed in both
Physical and Cloud Solutions
• The needs of merchants selecting Cloud and Physical can be mixed. There is no “one-size-fits-all”
• Cloud solutions are easier to deploy and adjust resources, but typically require more complexity to achieve the same transaction rate as physical hardware
18Where every interaction matters.
19Where every interaction matters.
Questions?
Frank DiRoccoProduct Manager, Peer 1 [email protected]
FOLLOW US ON TWITTER: @PEER1