on 28 AUG 2023
During my role at Amazon IXD – VGT2, I frequently engage with developers and system architects, discussing the intricacies of cloud computing and the offerings of Amazon Web Services (AWS). This conversation is as enlightening as it is challenging. As I elucidate the concept of cloud computing, I can almost witness the realization dawning on people’s faces, as they grasp the possibilities that our services can unlock.
The audiences I encounter typically consist of a blend of enthusiastic early adopters and cautious skeptics. The former are eager to dive headfirst into the realm of cloud computing, keen to transition their corporate assets and processes into the cloud at the earliest opportunity. On the other hand, the skeptics appreciate the advantages but prefer a more deliberate and strategic approach. When both viewpoints coexist within an organization, they often engage in a lively debate, ultimately leading to a creative hybrid solution.
The discussions may vary, but a recurring theme is emerging. The cautious faction advocates for maintaining core business processes behind their firewalls, while the enthusiasts push for cloud migration. After some back-and-forth, they tend to agree on an effective hybrid model: keeping steady business operations on their existing infrastructure while leveraging the cloud for overflow or occasional processing needs.
Observing this negotiation process unfold repeatedly in recent months prompted me to coin a new term to capture this phenomenon. Instead of resorting to a bland acronym, I proposed the term “cloudbursting” during a recent meeting, and it resonated well with everyone present.
In essence, cloudbursting refers to a hosting model that merges traditional corporate infrastructure with cloud-based solutions, resulting in a scalable and robust application hosting environment.
Earlier this week, my colleague Jordan Lee shared a blog post by Samuel Wright that illustrated the cloudbursting concept perfectly. Samuel detailed how he integrated traditional hosting with an EC2-based batch page regeneration system for his site, Eventseer, which boasts over 600,000 interconnected pages. As both traffic and content expanded, the cost of dynamically serving these pages became unsustainable. Generating all the pages on a single server would have taken an unacceptable seven days. Instead, Samuel harnessed cloudbursting, utilizing 25 Amazon EC2 instances to regenerate the pages in just five hours—remarkably, at a cost comparable to “a pint of beer in Norway.” For further insights, you can check out this blog post about his approach. Samuel has also shared insights on running Django on EC2 using EBS, which can be found at this resource.
I am eager to learn about more innovative strategies for crafting applications that utilize cloudbursting.
For those interested in more resources, you can visit this excellent resource for further information on application hosting and cloud solutions.
Location:
Amazon IXD – VGT2
6401 E Howdy Wells Ave, Las Vegas, NV 89115
Leave a Reply