Cloud Computing overview and case study
-
Upload
babak-hosseinzadeh -
Category
Technology
-
view
2.596 -
download
0
description
Transcript of Cloud Computing overview and case study
S b tiSome observations…
2
A few examples of web-scalabilityA few examples of web scalability
Source: http://www.compete.com
3
Google & Amazon are not the only ones…Google & Amazon are not the only ones…
Source: http://www.compete.com
4
Speed is a major differentiatorSpeed is a major differentiator
ec2-describe-imagesg
5
Living and socializing in a digital network economy…
6
A l k t th t iA look at the enterprise…
7
A quick review in the enterprise…m
plex
ityC
om
1970 2005
8
1970 2005
1970 2005Focus on “Data Processing” IT-led business innovation & transformationThe role of IT in the organization was simple Increasing demands, expectations, and business reliance on ITFew standalone apps in select departments Different types of solutions throughout the enterpriseA f i l l i h I l i diff l i & k
Bus
ines
s
A few internal users mostly in the same location
Internal users in different locations & geos, work arrangements, habits… + external interactions over different channels
Users had limited IT skills The business community is increasingly IT savvyB i i d b 9 5 (M F) 24X7 i i il bili d li biliBusiness operation used to be 9 – 5 (M-F) 24X7 connectivity, availability, and reliabilityControlled & predictable workload Less controlled & unpredictable workloadSystem availability & reliability requirements were simple and only effected the enterprise
Service Level Objectives are much more complex and impact the value chain
S ll f d Diff f d d l i
olog
y
Small set of vendors Different types of vendors and solutions
Simple technology stack Complex technology stacks A few low level languages and tools Different high level languages, multiple tools (i.e. CASE,
SLDC repositories, sophisticated compilers, interpreters…)i l l i h hi d
Tech
no Simpler solution approach, architecture, and implementation
“Enterprise Architecture”, multiple layers, distributed computing, exponential data growth, OO, SOA, EDA, Grid…
A few IT roles Multiple new roles, titles, and specialized skills
Central development with in-sourced resources Distributed development teams & hybrid sourcing models
9
p p y gIT operation & management used to be simple IT operation and management is much more complicated
IT investments & cost allocations
WW IT BenchmarkOn average, ~ 64% of IT Budget is spent on IT infrastructure
10
Cl d C tiCloud Computing
11
What is Cloud Computing?What is Cloud Computing?A pool of highly scalable, abstracted infrastructure, capable of hosting end‐
t li ti th t i bill d b
• Scalable, abstracted infrastructure• Hosting environment
customer applications, that is billed by consumption.
A style of computing where massively l bl IT l t d f ti d i f ti
• Utility-based billing
• Style of computing scalable IT‐related functions and information are provided "as a service" using Internettechnologies, potentially to multiple external customers.
y p g• Shared “services”• Internet accessible
Cloud Computing an emerging IT development, deployment and delivery model, that enables Cloud Services. Cloud Services: Consumer and Business products, services and solutions that are delivered and consumed in real‐time over the Internet
• IT development, deployment, & delivery model• Dynamic provisioning
12
y p g
Cloud Computing Model SolutionBusiness Capability
ControlFlexibility
Customization
13
Cloud Computing Vendor LandscapeCloud Computing Vendor Landscape
Note: Sample list of vendors
14
p
Cloud Computing Responsibility MatrixInfrastructure Hosting IaaS PaaS SaaS
Provider
Data Center Management
Hosting provider has the overall responsibility. Customers may negotiate location.
Subscriber has no idea… IaaSprovider abstracts the infrastructure.
Subscriber has no idea… PaaSprovider abstracts the infrastructure.
Subscriber has no idea… SaaS provider abstracts the infrastructure.
InfrastructureOperation & Management
Hosting Provider has the overall responsibility. Customers may negotiate specific terms.
IaaS provider handles the physical infrastructure, but the subscriber is responsible for image creation, operation and management.
(1) PaaS may run its own infrastructure(2) PaaS may partner with an IaaS providerIn both cases, it is abstracted from the subscriber
(1) SaaS may run its own infrastructure or partner(2) SaaS may offer its own PaaSor partnerIn both cases, it is abstracted from the subscriberfrom the subscriber. from the subscriber.
InfrastructureConfiguration / Customization
Hosting Provider offers a pre‐defined menu, but customers have the option pay for customization
Subscriber creates virtual images and manages the configuration & customization
PaaS provider offers somecapabilities for application configuration & deployment
N/A ‐ There is typically no infrastructure customization
I f H i P id ff b i T i ll i f N/A P S id ff N/A Th i i llInfrastructure Support
Hosting Provider offers basic support. Additional support can be negotiated.
Typically, infrastructure support is provided through forums. Premium support can be obtained, but Subscribers ultimately handle infrastructure support.
N/A – PaaS provider offers support for PaaS typicallythrough forums.
N/A ‐ There is typically no infrastructure customization
Application Development
N/A – Customer is responsible.
N/A – Subscriber is responsible N/A – Subscriber is responsible SaaS provider offers the solution
Application Customization
N/A – Customer is responsible.
N/A – Subscriber is responsible N/A – Subscriber is responsible SaaS provider offers some customization capabilities. 3rd
parties offer services
15
parties offer services.
Application Maintenance
N/A – Customer is responsible.
N/A – Subscriber is responsible N/A – Subscriber is responsible SaaS provider handles maintenance for all subscribers
Application Support
N/A – Customer is responsible.
N/A – Subscriber is responsible N/A – Subscriber is responsible Typically forums
An IT bill (tip included)An IT bill (tip included)
16
A Case study: Query Data Service
• Background• Financial Company• Multiple lines of business with some business processes interfacing 60+ external partners• Multiple lines of business with some business processes interfacing 60+ external partners• Mixed environment (packages, home grown apps, CICS, DB2, WAS, ALSB, …)
• Problem• Maintaining service SLA (Resp-time < 3 seconds + 99.99 availability)
17
Option 1 – Migrate existing data service to the Cloud
• Approach• Install & configure software packages in Amazon EC2• Route service requests to the Cloud
O d h i
• Notes• Had to figure out development & testing requirements• Had to assess for security & regulatory compliance• Had to size for servers
H d t f i l ft li t• Operate and manage the service• Benefits
• No hardware investment• Quick provisioning / hassle-free server • Built-in affordable scalability features (i.e. load balancing,
auto scaling)
• Had to pay for commercial software license costs• Had to figure out operations, support, change management, etc and
integrate them into the existing enterprise systems management framework (Tivoli & BMC)
• Had to figure out SOA Governance integration• Had to figure out secure data replication between on-premise database
& Cloud instancesFi t b d t & t
18
auto sca g)• Much better understanding of IT costs / service
• Figure out budget & payment• Had to evaluate disaster recovery• Client: Is this really Cloud Computing?
Option 2 – Redesigning existing data service for the Cloud
• Approach• Redesign the solution to leverage Cloud services• Route service requests to the Cloud• Operate and manage the service
• Benefits
• Notes• Had to figure out development & testing requirements• Had to assess for security & regulatory compliance• Had to size for servers• Had to pay for commercial software license costs
C f l l ti f SDB (i hit t l id ti• Benefits• No hardware investment • No software license costs for DB2• Anticipated lower operational costs (i.e. DB2 systems
administration)• Built-in affordable scalability features (i.e. load balancing, auto
scaling)
• Careful evaluation of SDB was necessary (i.e. architectural considerations, limitations, storage costs, etc)
• Had to learn SDB programming model• Had to figure out operations, support, change management, etc and
integrate them into the existing enterprise systems management framework (Tivoli & BMC)
• Had to figure out seeding SDB & secure data replication with on-premise database
19
scaling)• Enhanced understanding of IT costs / service
database• Figure out budget & payment• Had to figure out SOA Governance• Had to figure out how to abstract AWS to prevent vendor lock-in• Had to evaluate disaster recovery
Some important research & references…Some important research & references…
A review of enterprise projects by the Standish GroupCHAOS report: http://www.standishgroup.com/
http://mitsloan.mit.edu/cisr/ http://www.thomaslfriedman.com/
20
http://www.nicholasgcarr.com/
SummarySummary• Be careful in workload selection & analysis – Architectural decisions have to be analyzed
(i.e. transactionality)• Beware of the hype and misinformation – (i.e. don’t expect to just throw the applicationBeware of the hype and misinformation (i.e. don t expect to just throw the application
into the cloud and be done…Technology issues are relatively minor compared to business integration issues.)
• Understand and evaluate both on-premise & public cloud options - (i.e. Lots going on in the app server space including gridification and virtualization – Talk to your vendor to learn b t d d f t l )about roadmap and future plans).
• Should you move the particular app to the cloud or redesign it? Can it be cloud-sourced? --relatively straight-forward and simple, but best to strike an agreement with the inner circle quickly (i.e. an EA decision) to avoid continuing discussions, endless debates, etc…
• Assess impact/gaps on existing development testing deployment operation and• Assess impact/gaps on existing development, testing, deployment, operation, and maintenance processes – Tooling is critical for productivity and mandatory for cost-saving.
• A lot of the public cloud services have been in beta since a year ago or so…Before you dismiss too quickly, let’s put things in perspective. Beta in Cloud Services != beta in enterprise software. p
• Finally, irrespective of the business motivation, it is important to establish a baseline (i.e. avg transaction cost) for the existing workload and measure and compare thereafter to communicate the benefits using financial terms.
21
Thank you
22