2009/11/18

Devoxx 2009: Architecting Robust Applications for Amazon EC2

18/11/2009, Chris Richardson, SpringSource (VMware) www.cloudtools.org

Amazon EC2 cloud computing solution:
  • choose your virtual machine, with machine images of standard OS's
  • cloud services
    • SQS: Simple Queue Services
    • SimpleDB: alternative to relational DB
    • S3: storage
    • EC2 firewall: security groups
    • Elastic Block Storage:
      • replicated, mounted as device
      • snapshots → backup
    • Elastic Relational DB Service:
      • MySQL 5.2
      • maintenance window: 4hour/week
      • backup window
  • standard software: simply install (with yum or apt) your packages
  • console
  • local storage:
    • plenty (160GB → 1690 GB)
    • ephemeral
    • slow down on first access
    • → Elastic Block Service
  • easy upgrades:
    • clone your production environment
    • upgrade the clone
    • test the clone
    • if OK: put the clone in production
    • remove the old clone
  • regions:
    • US
    • EU
    • Asia
    • sub-zones:
      • “availability zones” that are isolated from each other.
      • better availability
      • more expensive
issues:
  • security:
    • not PCI-compliant
    • discomfort of putting your core data on the cloud
    • where is your data really?
    • but:
      • Amazon experience
      • unlimited logging
      • standard best practices for security
      • isolated instances
      • put servers in different security groups → Amazon EC2 firewall
      • encrypt your data and backups
  • cost:
    • expensive for large servers
    • bandwidth
    • but: no extra cost of cooling, power etc.
  • machines:
    • no very small, very big machines
    • maintenance windows
    • load-balancing:
      • ipbased: no support for sessions
      • dns (cname)
  • is it reliable?
    • is internal IT better?
    • Amazon expertise
    • easy to launch a new instance within a few minutes
future:
  • Platform as a Service:
    • complete stack
    • simpler scaling, without being involved into the technical details
    • Google Application Engine
    • Cloud Foundry:
      • Spring & Grails

No comments: