Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I setup two instances of my application on EC2, and have been using S3 in as a local-to-AWS backup and media asset delivery. We moved over about 15% of our applications content/traffic to EC2 in mid-June. The result is mixed, and we are moving the content heavy usage instance back to our hosted data center, and now are investigating other content delivery options.</p> <p>Do note that:</p> <ol> <li>My application is bandwidth hungry (starting at 100mbps per instance) </li> <li>My company and I are based in Switzerland and that surely has had an impact on our evaluation.</li> <li>I define bandwidth as a rate of flow (mbps, etc.) and traffic as volume (mb, gb, etc.)</li> </ol> <h2>Pros:</h2> <ul> <li>Traffic costs for low to medium volumes, assuming less than maybe a terabyte per month. Exceed that fuzzy line and either do it yourself or find a proper CDN</li> <li>Active user community</li> <li>Effectively unlimited bandwidth with S3/CloudFront-delivered content</li> <li>Flexibility (kick off an instance and have it running in minutes)</li> <li>CPU power available in an instance, even the small instance type, was always enough for my application. There are other high-CPU instance types for those who need it.</li> </ul> <h2>Cons:</h2> <ul> <li>We had an instance become unreachable (a not unheard of occurrence) and had execute our disaster recovery procedure. 12h.</li> <li>Network latency, for both S3 and EC2, can be unacceptably high (100s of ms)</li> <li>EC2 instance bandwidth is limited. Despite hours of search, I never found an official statement with hard numbers one what users can expect. Initially we saw a max of ~250mpbs in tests but that seems to have improved dramatically.</li> <li>Per HTTP connection bandwidth can be unacceptably low. 1-2mbps from even our Swiss data center with a 800mpbs connection and quality peering. EDIT: We have recently seen rates between our data center and EC2 in the 3-4mpbs range.</li> <li>S3 is not a 'normal' file system<strike>, and special software is required. We chose JungleDisk, which I now find inappropriate for a 24/7, moderately sized data set server environment. Strange things would happen (file listed twice with an 'ls' command) and unexpected crashes. </strike> Use <a href="http://aws.amazon.com/ebs/" rel="noreferrer">EBS</a> for persistent data, although that is <a href="http://teddziuba.com/2011/04/amazon-the-purpose-of-pain.html" rel="noreferrer">not without caveats</a>. </li> <li><strike>S3 is <em>not</em> a CDN. My company, like many others, have tried to use Amazon S3 as a CDN. There are other low cost alternatives out there. (Akamai, voxel.net, easycache.com) </strike></li> </ul> <p>I'm a fan of the cloud concept, and we will continue to run an instance out of EC2, but we found it inappropriate for our main production needs in its current form. AWS has some issues to sort out.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload