architecting enterprise solutions in the cloud

Architecting for the CloudBuilding real Enterprise Class Solutions

www.twitter.com/madgreek65

www.facebook.com/mike.kavis

www.linkedin.com/mikekavis

www.kavistechnology.com/blog

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

Cloud ComputingIt’s only as good as the team that designed it

People fail, not technology

It’s all about architecture,Regardless if it is on-premise or off-premise

There are no silver bullets

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 ArchitectureDomain 1: Cloud Computing Architectural FrameworkSection II. Governing in the CloudDomain 2: Governance and Enterprise Risk ManagementDomain 3: Legal and Electronic DiscoveryDomain 4: Compliance and AuditDomain 5: Information Lifecycle ManagementDomain 6: Portability and InteroperabilitySection III. Operating in the CloudDomain 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?• Predictable or Unpredictable?• Distributed or Centralized ?• # transactions per second• Expected response time

Define Platform Requirements

Data:• Real-time, near real-time, delayed ?• Security & Compliance Constraints• Relational, Sequential,

Transactional ?• Public or Private ?• Retention length

Define Platform Requirements

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

Architectural Decisions

Resources

Budget

Time

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 ?