Modern internet infrastructure are complex.  Components and services are prone to failure.  Resiliency involves building redundancy, best practices and processes into your architecture to make you able to bend and not break.

• Migrating to cloud service providers
• Rearchitecting and refactoring applications to scale
• Scaling the database tier - MySQL and Oracle
• Building redundancy into every layer
• Deploying object caches - memcache
• Deploying page caches - varnish
• Migrating to Innodb - transactional storage engine
• Infrastructure design
• Infrastructure automation
• Disaster Recovery
• Business Continuity with cloud deployments

Call or Skype us in New York City +1-212-533-6828

1. Backup outside of the Cloud

Some of the high profile companies affected by Amazon's April 2011 outage could have recovered had they kept a backup of their entire site outside of the cloud.  With any hosting provider, managed traditional data center or cloud provider, alternate backups are always a good idea.  A MySQL logical backup and/or incremental backup can be copied regularly offsite or to an alternate cloud provider.  That's real insurance!

2. Use alternate regions and availability zones

Amazon's outage in April …

Deploying in the Amazon cloud is touted as a great way to achieve high scalability while paying only for the computing power you use. How do you get the best scalability from the technology?

1. Use Auto-scaling

Auto-scaling is a unique feature of cloud computing and Amazon's EC2 offering. Setup a load balancer and a couple of webservers for your application as you normally would. Design your webserver based on a template AMI that you'll reuse over and over. Then setup auto-scaling and set thresholds based on the traffic you forecast. When a threshold is passed, AWS will spinup a new instance of your webserver, and roll it into the load balancer pool automatically. Once traffic falls below the scale back threshold, Amazon will take a server out of the pool for you.

Be sure to monitor this …