Best Times to Use Amazon Web Services (AWS) vs. a Fixed Environment

Amazon provides resources on demand, giving IT teams the flexibility to use compute resources whenever they need, as much as they need. Netflix, Amazon’s biggest customer, decided to limit investment in its own data centers and migrate to AWS to better handle traffic spikes on its streaming service.  Start-ups in Silicon Valley and around the world are embracing AWS as well, due to the flexible cost structure and unlimited resources it provides. While it is a great solution in many cases, there are times when a more traditional, fixed environment may be a better fit for the requirements.

Here are the best uses for each type of setup.

When it makes sense to consider AWS:

• Applications that have large bursts and need a high degree of scalability
• Infrastructure is run on either Windows or Linux
• Able to run application in multiple zones (highly available)
• Running non-mission critical system (if not highly available)
• If there is flexibility with cost increases/decreases month-to-month
• Application can leverage global connectivity- Amazon CloudFront (CDN) to deliver content locally to end users

When a fixed environment may be more appropriate:

• Consistent need of compute resources
• Costs must remain flat or be predictable month-over-month
• Application cannot be migrated to AWS
• Strict security or compliance requirements such as HIPAA Compliance, FISMA, and PCI
• Have a specific licensing structure (Example: Oracle)
• Using an operating system besides Windows/Linux

Fortunately with Connectria you can run both types of environments with complete 24/7 support, something that is pretty unique in the hosting industry.  Get more information on Connectria’s Managed AWS Solution.

If you have additional examples for either type of environment please add a comment below and we’ll be happy to update this post.