Upcoming Events

Cloud Connect
Santa Clara
Feb 13-16, 2012

Cloud Connect brings together the entire cloud eco-system to better understand the transformation we're experiencing and promises to be the defining event of the cloud computing industry. Learn about the latest cloud technologies and platforms from thought leaders in Cloud Connect’s comprehensive conference.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up

Vendor NewsFeed

More Vendor NewsFeed »

Email Email  Print  Share


FireHost Flexes Its Cloud Scaling Options

Tags: , , , , , , , , , , , , , ,

Channel: Private Cloud, Security, Cloud Computing, Public Cloud

FireHost is extending its scaling options, adding a scheduling capability to its cloud service offering. In addition to scaling on demand, the scheduled scaling feature lets customers that can predict demand manage capacity more effectively.

Auto-scaling allows customers to set thresholds of cloud server utilization so that, if an unexpected spike occurs, the application automatically scales. However, to allocate the resources to a server, each server is required to reboot, causing a potential 30 seconds of downtime. "Going dark for even 30 seconds during a peak can be troublesome, and the third scaling feature, scheduled scaling, addresses this," says Jason Verge, research analyst, hosting, Tier1 Research, said

The scheduling feature is as easy to use as Microsoft Outlook, says FireHost. Unlike the auto-scaling option, which is considered more of a fail-safe mechanism for unexpected spikes, customers can plan when to scale up and down based on time of day. The scheduled events can be set as one-time or as repeating events at an interval of the customer's choosing. The company says customers can also add multiple servers to any event, and scheduled events that contain multiple servers also provide the ability to set the reboot order.

Scheduled scaling is a smarter way to adjust infrastructure proactively, says Verge. "The schedule scaling feature better addresses the needs of customers with somewhat predictable traffic spikes than the autoscaling feature does. While the autoscaling capability provides a great safety net for unpredictable traffic spikes, there is potential for a slight delay when scaling up as the server reboots itself. For certain customers, even that slight delay can be troublesome, forcing them to manually configure scaling ahead of each predicted spike. For potential and current customers who have a reasonable intelligence as to their traffic patterns, scheduled scaling saves them time over configuring this manually, each and every time."

He says the trend in the dedicated hosting space is to automate as much as possible. This is FireHost approaching the problem from the other direction, providing the security and management benefits of hosting on dedicated hardware atop of cloud rather than trying to "cloudify" a dedicated hosting setup. "This is just as flexible and secure as a much more costly managed private cloud--the only other option comparable in terms of this level of security and flexibility," he says.

While the company doesn't expect all of its customers to embrace the new capability, it does expect it will appeal to a lot of them. In the month since its release, about 20% of its customers are using scheduled scaling.

See more about "RESEARCH: Physical And Logical Security Convergence" by subscribing to Network Computing Pro Reports (free, registration required).

Related Stories

Related Reading


More public-cloud-tech-center Insights



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Public Cloud Reports

Premium Content

Research and Reports

Hypervisor Derby
August 2011

Network Computing: August 2011

TechWeb Careers