Architecting enterprise solutions in the cloud

  • 2,540 views
Uploaded on

 

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,540
On Slideshare
0
From Embeds
0
Number of Embeds
2

Actions

Shares
Downloads
44
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. 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
  • 2. I’m MAD!
  • 3. Current State of the Cloud:
    Cloudy with 100% chance of Confusion
  • 4. Vendor Hype
    To the Cloud
    Me Too Mega Vendors
  • 5. Critics & FUD
    (Fear, Uncertainty, Doubt)
  • 6. IT Blunders
  • 7. People fail, not technology
    Cloud Computing
    It’s only as good as the team that designed it
  • 8. There are no silver bullets
    It’s all about architecture,
    Regardless if it is on-premise or off-premise
  • 9. Let’s focus on Architecture!
    What is the desired future state?
  • 10. Step 1: Answer one question….“What problem are you trying to solve?”
  • 11. Step 2: Create a business architecture
  • 12. Step 3: Identify Requirements
  • 13. Step 4: Learn the Pros and Cons of the various Cloud Models
  • 14. 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
  • 15. Define Platform Requirements
    Network traffic:
    • Chatty or Chunky?
    • 16. Static or Dynamic?
    • 17. Predictableor Unpredictable?
    • 18. Distributed or Centralized ?
    • 19. # transactions per second
    • 20. Expected response time
  • Define Platform Requirements
    Data:
    • Real-time, near real-time, delayed ?
    • 21. Security & Compliance Constraints
    • 22. Relational, Sequential, Transactional ?
    • 23. Public or Private ?
    • 24. Retention length
  • Define Platform Requirements
    Reliability:
    • 24x7x365 ?
    • 25. SLAs
    • 26. Guaranteed delivery ?
    • 27. How long can you be down?
  • High Speed Decisions
    Typical trade-off decisions?
    • SQL or NoSQL ?
    • 28. In-Memory solutions – minimize disk i/o
    • 29. Amount of control of servers, OS, App servers, etc.
    • 30. Control of network configuration
    • 31. Server sizes (CPUs, memory, disk)
    Usually requires IaaS
    • More control of the stack
    • 32. Not forced into a specific dev environment
  • Decisions and Trade-offs
    Requirements
  • 33. Cloud Computing – Hybrid Clouds
  • 34. Full Redundancy & “Infinite” Scalability
  • 35. PCI in the Cloud
  • 36. Everything as a service
  • 37. Summary
    • It’s all about architecture!
    • 38. Everything fails, plan for failure
    • 39. Leverage cloud strengths
    • 40. Architect for cloud weaknesses
    • 41. Solutions are like fingerprints, no two are the same
  • Any Questions ?