Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

Dispelling the myths of hybrid hosting

Emil Sayegh, CEO, Codero Hosting | Oct. 9, 2015
Hybrid hosting lets you run your database on dedicated servers, put your front-end in the cloud, and tie everything together with a single click.

This vendor-written tech primer has been edited to eliminate product promotion, but readers should note it will likely favor the submitter’s approach.

When the Amazon Web Services platform failed recently some of the internet’s biggest sites -- including Netflix and Tinder – suffered extended outages. The culprit? AWS's NoSQL database DynamoDB, where increased error rates led to increased errors and latency in more than 20 AWS services.

These and other sites wouldn’t have had a problem if they used hybrid hosting, the best way to architect modern apps. Hybrid hosting lets businesses set up their databases on dedicated servers, put their front-end Web apps in the cloud, then tie everything together with a single click.

While many companies recognize that hybrid hosting and the hybrid cloud are “the next big thing” in hosting, some are intimidated by what they don’t know. Because hybrid cloud adoption is still nascent, there remains a lot of confusion about the technology. It’s time to debunk some myths.

Myth: Hybrid cloud is only used for cloud bursting.

When an application running in a private cloud gets a sudden demand for computing capacity, it can “burst” to a public cloud to handle that spike. This cannot be a reactive measure, though, and it is difficult to run applications on traditional, dedicated servers and then swap that same workload to the cloud at will. For cloud bursting to work properly, applications must be designed from the ground up with that in mind; the vast majority of applications are not built this way. It takes special skill and intent to build applications that know how to burst to the cloud.

Hosting on a hybrid infrastructure does not magically make an application cloud burst; the application must be designed for that. Furthermore, the hybrid cloud must allow for the cloud burst at the networking level, which requires integration of hybrid at the networking level. It is unreasonable to expect legacy applications running on traditional dedicated servers to just swap their workloads to the cloud on demand.

Hybrid cloud cannot, in fact, be used for cloud bursting unless the application was designed for that. Combining an adequately designed application with a hybrid cloud infrastructure, however, would enable an organization to build up an auto-scaling and burst-capable application on hybrid cloud infrastructure.

Myth: Hybrid cloud is complicated to implement.

This is only true if hybrid cloud is done in a non-automated, non-productized manner. If an organization attempts to build its own configuration, things can get complicated quickly and it can take weeks to implement. However, when hybrid cloud technology is implemented through an automated platform, it can be done in less than a few hours, if not minutes.


1  2  3  Next Page 

Sign up for MIS Asia eNewsletters.