royans

  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

Small organizations often keep a very active online presence . For them, any news is good news. Larger organizations however try to be opposite of that and control information. What I’ve been trying to understand is how in spite of all that companies like Google and Microsoft still manage to have a huge online presence. No.Of.TwitterAccounts= (Size.Of.Company)^(1/2)  ? For example today, Google announced a list of all of its Twitter accounts in one page.  How do they do it ? General twitter.com/Google - our central account twitter.com/Blogger - for Blogger fans twitter.com/GoogleCalendar - user tips & updates twitter.com/GoogleImages - news, tips, tricks on our visual image search twitter.com/GoogleNews - latest headlines via Google News twitter.com/GoogleReader - from our feed reader team twitter.com/iGoogle - news & notes from Google's personalized homepage twitter.com/GoogleStudents - news of interest to students using Google