Category: CommunityHigh-Availability Load Balancing At A Fraction Of The Price

Share this post...Tweet about this on TwitterShare on Google+0Share on Facebook0

This post is part of a series comparing InterWorx to other server and hosting management applications. Today,  we’re going to take a look how InterWorx, compares to other enterprise scalability solutions. Interworx is a high-availability load balancer capable of providing enterprise-grade scalability at a tenth of the price of competing load balancing products.

If you’d like to see a detailed comparison of InterWorx 5 with other server management products, take a look at our comprehensive comparison matrix.

You have a very popular site or group of sites, or you provide hosting for someone who does. One server isn’t enough so you go looking for load balancing solutions. You peruse the prices of various enterprise load balancing solutions—and you have a mild cardiac event. The least expensive of them costs well over $5000, and that’s just for the hardware—support and software updates bring the operating cost up into the tens of thousands of dollars.

We’re going to have a quick look at how InterWorx compares to other enterprise load balancing applications. In other articles of this series, we’ve compared InterWorx to server and hosting management applications like cPanel and Parallels Plesk. This article is going to be a little different, because none of the usual suspects offer high-availability load balancing.

InterWorx Cluster Management

So, we’ll be talking about three of the leading enterprise load balancing applications, which are:

  • Barracuda ADC 540
  • Brocade ADX 1000
  • F5 BIG-2000

Each of these are high-end load balancers capable of supporting at least 100 servers. InterWorx isn’t quite in that category: it supports a maximum of 50 servers, but that’s quite enough for most common web hosting scaling scenarios.

InterWorx and each of the example applications are capable of high-availability load balancing, which means that not only can they load balance between multiple servers, they can also be configured with a redundant load balancer that takes over in the event of a problem with the primary: redundant servers with redundant load balancers makes for a highly reliable and scalable hosting platform.

Price is the major differentiating factor here.

The Barracuda ADC 540 has upfront hardware costs of $6,999, with annual support payments of $1,549, and annual update costs of $1,249. We’ve calculated the three-year total cost of operating for this product to be $31,971.

The Brocade ADX 1000 has upfront hardware costs of $32,779, with a three-year cost of operating of $66,758.

The F5 BIG-2000 has upfront hardware costs of $21,012 with a three-year cost operating of $48,328.

See our load balancer comparison matrix for sources and methodology.

InterWorx has a number of advantages that other enterprise load balancers do not have.

  • It can run on commodity hardware. You’ll want a decent server, but it needn’t cost $30,000, and
  • The InterWorx load balancer can double up as a file server or database server.

InterWorx is capable of acting as a high-availability load balancer with a maximum throughput of 1 GBPS. InterWorx’  three year cost of operating is $3,420, which comprises $299 for an annual support package and the cost of redundant commodity servers. Software updates are free and there is no replacement cost.

InterWorx is a capable and inexpensive alternative to overpriced enterprise load balancing applications, offering powerful scalability at a fraction of the price.

This post is part of a series in which we look at how InterWorx compares to other leading server management applications. There are more to come, so subscribe to the feed or follow us on Twitter or Facebook to hear the latest.

Sep 30, 2014, 12:32 pmBy: Corey Northcutt (0) Comments

Leave a Reply
Surround code blocks with <pre>code</pre>

Your email address will not be published.


Sign up to receive periodic InterWorx news, updates and promos!

New Comments

Current Poll

  • This field is for validation purposes and should be left unchanged.