| InformationWeek Analytics (September 2008) |
“As traffic and content grew, serving up the pages dynamically became prohibitively expensive, so Røst decided to use an array of 25 Amazon EC2 instances in a “cloudburst” arrangement for static file generation and background processing jobs. The savings benefit from not having standby dedicated servers was immediate and lasting, Røst says.”
–Roger Smith |
| DevCentral (September 2008) |
“A hybrid approach like cloudbursting seems to be particularly appealing. Enterprises seem reluctant to move business critical applications into the cloud at this juncture but are likely more willing to assign responsibility to an outsourced provider for less critical application functionality with variable volume requirements, which fits well with an on-demand resource bursting model. Cloudbursting may be one solution that makes everyone happy.”
–Lori MacVittie |
| Amazon Web Services Blog (August 2008) |
“Cloudbursting is an application hosting model which combines existing corporate infrastructure with new, cloud-based infrastructure to create a powerful, highly scalable application hosting environment. Earlier this week my colleague Deepak Singh pointed me to a blog post written by Thomas Brox Røst. In the post, Thomas talks about how he combined traditional hosting with an EC2-powered, batch mode page regeneration system. His site (Eventseer) contains over 600,000 highly interconnected pages. As traffic and content grew, serving up the pages dynamically became prohibitively expensive. Renerating all of the pages on a single server would have taken an unacceptably long 7 days, and even longer as the site became more complex. Instead, Thomas used a cloudbursting model, regenerating the pages on an array of 25 Amazon EC2 instances in just 5 hours (or, as he notes, “roughly the cost of a pint of beer in Norway.”).”
–Jeff Barr |
| High Scalability (August 2008) |
“Static files have the advantage of being very fast to serve. Read from disk and display. Simple and fast. Especially when caching proxies are used. The issue is how do you bulk generate the initial files, how do you serve the files, and how do you keep the changed files up to date? This is the process Thomas covers in his excellent article Serving static files with Django and AWS – going fast on a budget”, where he explains how he converted 600K thousand previously dynamic pages to static pages for his site Eventseer.net, a service for tracking academic events.”
–Todd Hoff |
| Google App Engine Blog (June 2008) |
“Many developers have written useful articles tutorials about App Engine. […] Thomas Brox Røst wrote an article that outlines porting the data of an existing Django App to App Engine.”
–Marzia Niccolai |