ecommerce series part 3 - application deployment
Post on 15-Jan-2017
161 Views
Preview:
TRANSCRIPT
Ashwinee Kumar
Jun 2015
Application Deployment in Cloud and underlying technologyEcommerce Series – Part 3
Ecommerce deployment architecture
3
1. One IP address per ecommerce2. Global Server Load Balancing (GLSB)
• Hosted as a standalone service• Hosted as part of a Content Delivery Network (CDN)• Appliance based, residing in an on-premises data center
Brining up server – Deployment (115)
6
Types of Deployment Snapshots – images – ofv, ami etc..
Quickly build server, capture intricate changes, test and archive snapshots for audit No ability for Patching and maintenance
Archives – tar, zip, rar Works well for installation under one root directory and does not span across file
system Source files
Deployment Unit Snapshot Archive Source
Monitoring the Deployment
7
System monitoring Application monitoring – configuring alerts in Load balancer
Component monitoring – HTTP port health through ping Superficial and limited scope
Page/resource monitoring – home page responds with HTTP 200 Limited scope and does not ensure entire app is tested
Dynamic test page to test basic functionality of the app Adding product to cart, querying for product, execute query against search engine
Virtualization
9
1. Partitioning – Maximizing utilization1. two hardware threads per physical CPU core, 12 cores per processor, and two processors
per physical host - 48 servers2. Isolation – Non interference3. Portability – Of live application across servers and cloud during maintenance and peak load
Virtualization offers you the ability to partition a physical server into many
smaller servers, with each virtual server isolated from other virtual servers on
the same physical server.
Types of Virtualization
10
Full virtualization - hypervisor is installed directly on bare metal
Para virtualization - kernel works cooperatively with the hypervisor to pass through certain calls directly to the underlying hardware
Operating system virtualization - very light hypervisor is installed on the operating system itself
CDN
13
Large distributed networks of servers that accelerate the delivery of your platform to your customers• Deliver static content to the user from the server nearest to him• Proxy HTTP requests back to your data centers • Optimize the delivery of content through advanced functionality• Caching entire web page response• Cache API calls response• Value adds including firewall, GSLB• With most content delivered from CDN, very little of your data center is
exposed for security threat
CDN is not IaaS as they don’t originate the content they serve
150 of the average 151 http calls are for static content
What can you publish in CDN?
14
• All static content including html, css, js• Pages with dynamic content - Entire page on CDN and making ajax calls to
generate dynamic content. Eg.. Hello <Name>• Different version of each page – CDN has capability to look into http header
for say Geo location• Unique Search results pages – based on search key
Essentially most of your platform can be served from CDN
top related