Whether you use the Cloud or dedicated servers, you should always make sure you have a plan for your configuration in the event that something goes wrong. This is a series of posts based on a discussion I had with Aaron Scheel, a solutions engineer here at Rackspace.
Whether you use the cloud or dedicated servers, you should always make sure you have a plan for your configuration in the event that something goes wrong. This is the first in a series of posts based on a discussion I had with Aaron Scheel, a solutions engineer here at Rackspace.
1. According to research, a 1-second delay in page load time equals a 16% decrease in customer satisfaction, and a 7% loss in conversions. Meaning a site that usually earns $100,000 a day could lose up to $2.5 million a year.
More and more businesses are shifting from using cloud computing solely for testing and development to extending pieces of their production environments into the cloud. With this shift, IT decision makers are now faced with a whole new set of considerations.
Every time I talk to customer that is joining the Racker family or run’s into an issue with scaling their IT infrastrcuture, I find that they either don’t know how backup and storage needs will effect their business or how to best enable today’s storage product’s to better enable their business needs. It seems that when it comes to architecting the largest most bullet proof solution in the world either the storage portion or the backup solution are thought of last. Don’t get me wrong, I can understand why this is the case and in most case understand why it is the last thing to consider. However I would like to recommend a new way to think about architecting your solution when storage or backup is needed.