Cloud architecture: Notes from an Amazon talk
Some notes from a talk I was at. Didn’t get time to write it in detail. But hey, something is better than nothing… right ? Design for failure - handle failure - use elastic ip addresses - use multiple amazon ec2 availability zones - create mutliple database slaves across multiple zones - use real-time monitoring (amazon cloudwatch) - use amazon EBS for persistent file system - snapshot database to s3 (from ebs) Loose coupling sets you free - independent components - design everything as a blackbox - de-coupling for hybrid models - loadbalance-clusters - use SQS as buffers to queue messages. Allows elasticity Design for dynamism - build for changes in infrastructure - Don't assume health of fixed location of components - Use designs that are resil