Architecting enterprise solutions in the cloud

Architecting for the CloudBuilding real Enterprise Class Solutions
www.twitter.com/madgreek65
www.linkedin.com/mikekavis
www.kavistechnology.com/blog
www.facebook.com/mike.kavis

I’m MAD!

Current State of the Cloud:
Cloudy with 100% chance of Confusion

Vendor Hype
To the Cloud
Me Too Mega Vendors

Critics & FUD
(Fear, Uncertainty, Doubt)

IT Blunders

People fail, not technology
Cloud Computing
It’s only as good as the team that designed it

There are no silver bullets
It’s all about architecture,
Regardless if it is on-premise or off-premise

Let’s focus on Architecture!
What is the desired future state?

Step 1: Answer one question….“What problem are you trying to solve?”

Step 2: Create a business architecture

Step 3: Identify Requirements

Step 4: Learn the Pros and Cons of the various Cloud Models

Step 5: Chose cloud model(s) and refine requirements accordingly
Read this  CSA Guide v2
Section I. Cloud Architecture
Domain 1: Cloud Computing Architectural Framework
Section II. Governing in the Cloud
Domain 2: Governance and Enterprise Risk ManagementDomain 3: Legal and Electronic DiscoveryDomain 4: Compliance and AuditDomain 5: Information Lifecycle ManagementDomain 6: Portability and Interoperability
Section III. Operating in the Cloud
Domain 7: Traditional Security, Business Continuity and Disaster RecoveryDomain 8: Data Center OperationsDomain 9: Incident Response, Notification, and RemediationDomain 10: Application SecurityDomain 11: Encryption and Key ManagementDomain 12: Identity and Access ManagementDomain 13: Virtualization

Define Platform Requirements
Network traffic:
Chatty or Chunky?
Static or Dynamic?
Predictableor Unpredictable?
Distributed or Centralized ?
# transactions per second
Expected response time

Data:
Real-time, near real-time, delayed ?
Security & Compliance Constraints
Relational, Sequential, Transactional ?
Public or Private ?
Retention length

Reliability:
24x7x365 ?
SLAs
Guaranteed delivery ?
How long can you be down?

High Speed Decisions
Typical trade-off decisions?
SQL or NoSQL ?
In-Memory solutions – minimize disk i/o
Amount of control of servers, OS, App servers, etc.
Control of network configuration
Server sizes (CPUs, memory, disk)
Usually requires IaaS
More control of the stack
Not forced into a specific dev environment

Decisions and Trade-offs
Requirements

Cloud Computing – Hybrid Clouds

Full Redundancy & “Infinite” Scalability

PCI in the Cloud

Everything as a service

Summary
It’s all about architecture!
Everything fails, plan for failure
Leverage cloud strengths
Architect for cloud weaknesses
Solutions are like fingerprints, no two are the same

Any Questions ?

http://www.kavistechnology.com	1096
http://www.solutionsarchitect.ca	24
http://feeds.feedburner.com	22
http://nimaro.solutionsarchitect.ca	11
http://nimaro.systemsintegration.ca	9
http://www.rkmadan.com	5
http://translate.googleusercontent.com	3
http://nimaro.systemsintegration.com	1
http://feedproxy.google.com	1
http://www.enterprisesolutionsarchitect.com	1
http://www.google.com	1

Architecting enterprise solutions in the cloud

by Mike Kavis on Jun 19, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

11 Embeds 1,174

Statistics

Architecting enterprise solutions in the cloud — Presentation Transcript