Tangent Thought Gallery

Some things just aren’t as easy as you’d think they should be. If you’ve been involved with web hosting much, you know it fits that scenario well. Assuming you’ve gone over the info in part 1 of this series (which is a fairly high level view of things), let’s do a fly over still another upper level issue: “Precisely what type of hosting are you looking for?”

There are essentially three options:

1. Self hosting
2. External hosting
3. Blended (some degree of both)

I believe there are few instances where self hosting makes sense. If you think your business case is one of those unique situations that call for it, you’re probably wrong. Sorry. Please contact me and I’ll be glad to try to dissuade you.

Options with External hosting broaden the choices even further. At the outset, your basic hosting options are:
1. Shared—the hardware is transparent to you; you’re just buying a service level agreement (SLA); your site may be in the same hardware as Sally’s Muffin Boutique & Laundry or less socially innocent entities, however, that shouldn’t be a concern (the servers are probably virtualized at this point anyway—but that’s something you should check out)
2. Dedicated—the hardware is yours (leased) and yours alone; you needn’t be concerned with anyone else being on your hardware-BUT-you need to handle or arrange with your provider for all hardware contingencies such as DR, fail-over, hardware failure, etc.
3. Collocation—this can be interpreted as just space in a rack where part of the SLA is power, environmental (temp, humidity, security), and telco connectivity; it can also be expanded to include cages for your equipment at the hosting site, even rooms full of your equipment if your demands are large enough

The complexities swoop in almost immediately. Trying to make things simpler, however, in the next post of this series I’ll directly dive into the type of hosting in which 80%+ of most business are interested; if you’re looking to simply set up shop on the net with some added content management functionality and you’re looking for only a moderate investment and want to avoid recurring IT costs, stay tuned. I’m hoping to make that simple(r) for those in this camp. Until then, let’s take a peek at just a few (there are a lot more than those shown here!) of the tangent considerations with hosting…

Required service level (e.g., “four 9s”, or 99.99% uptime? More? Less? Perhaps better asked: “How much will that downtime cost my business annually?“)—be sure to read and understand what your hosting provider means in their SLA statement. You don’t want surprises, particularly if your revenue stream is coming through that channel.

Managed Services—this is where you can leverage your provider’s talent pool so you don’t need to staff up. Sure, you’ll want them to handle the hardware on the inside, especially if you’re not doing collocation, but to what extent? Backups, disaster recovery, etc.—to what degree are they involved? How about security patches? If you’re systems get a little trickier, let’s say with clustering and virtualization, what’s their involvement? There’s really a continuum here, from rudimentary hdw/OS admin support to comprehensive application support outsourcing. Get that nailed down clearly in any contract before signing; you don’t want confusion downstream. Also be sure you know how and who to call, along with who is empowered on your side to contact the provider and what type of support to expect.

Facility Access—this should only be a consideration for collocation or, upon rare occasions, dedicated hosting but you’ll want to understand the processes involved as well as which members of your team can get access, how they get access, and when.

Package Options—this can get tricky in its own right but basically, if you’re dealing with managed solutions, you have to determine what you’re leasing, from hardware to application software. It can all be accommodated for a price.

You should note that as the optional hardware, OS, utilities, and application packages mount up, so do associated costs for support. It’s still typically more cost effective than staffing for this yourself.

Almost a given in web hosting is that you’ll change your provider more than once and your model of operation more than twice so all this becomes relevant sooner or later. In the next post well cover shared hosting consideration since it’s probably the most popular.

Web hosting reminds me of home insurance. Everyone knows they need it. If you’re feeling lucky or you enjoy the adrenaline rush of huge risks, you tend to take a minimalist view. If you’re a pessimist or if you just happen to have experienced enough of life’s uncertainties then you get a bit more pragmatic. Our home was destroyed by a tornado several years ago. As you can imagine, even though our family thankfully emerged unscathed, the recovery for us and our entire neighborhood was daunting. Sadly, some of our neighbors found out at that time that their “bargains” on insurance weren’t such a deal after all.

The same applies to hosting. It’s funny that, although the question of “what’s the best host for __x__?” is one of the most frequently asked questions on networking sites, after a thorough answer it’s typically voiced with a subsequent follow up “oh (insert awkward silence here)…well, I really wasn’t meaning to spend that much!” Please understand I’m not advocating coming to your hosting options without concern for costs, but these must be put into perspective: what are you hoping to accomplish and how many headaches do you want to still entertain once online? We are talking about your most ubiquitous customer touch point, right? If you’re engaging in online commerce, we’re talking about revenue streams and customer satisfaction, right?

Since this is actually a large topic, my plan is to summarize top level issues in this post and, if time allows, get more granular in a subsequent post or two.

Decision matrix #1—questions to ask yourself at the outset:
1. Security and reliability—you need to start with these seemingly less exciting points, imo, compared to features, etc. Do you have critical, private data you’ll be storing on a database? (And please don’t tell me you’ll be storing credit card data—ever!) If you’re storing sensitive data, move away from shared hosting, unless, of course, you’re operating on shared servers with independent virtual servers. The related topic of performance, particularly of virtual database servers is important but out of scope for this post. What about DR? How is that handled and what’s the expected worse case scenario for downtime?
2. Features—what components, tools and tangential systems are on my “must have” list vs. those provided or available? Are these extensible? Can these be at all integrated with my back end systems? Are there business user tools available or does all interaction need to come through my internal IT support? Do I need internal IT support or can I better use those resources elsewhere?
3. Support—what is the support structure of the provider? Who do I contact and how? Who within my organization can make support calls? What is the skill set of those on support? How about level 2 & 3 support? What are their expectations of me and my staff? If needed, can I get someone on the phone 24×7 or am I limited to email or online chat support?
4. Qualifications—who are some of your hosting provider’s customers? You may not yet be an IKEA or Barnes & Noble, but your provider should be able to suggest success stories for organizations roughly similar to yours. Additionally, if they’re doing only commerce, they should already have already successfully passed PCI compliance audits, so you may want to ask about that as well.
5. How much involvement can you afford? — Specifically, your own tech resources staffed to maintain the operation. My opinion, you can rarely afford to staff adequately with your own resources so lean heavily on managed service providers. They’re really cheap at the price. Unless you originally got into business with the dream and end goal of running a data center.
6. Along the lines of “why did you get into business in the first place?” and “what are your core-competencies?” do you really want to own any hardware or software? Probably not, so move away from collocation. If you convert these costs (often capitalized) into monthly expenses as part of your lease/managed services agreement, you may find increased appeal on the financial end.

Assumption: most people will find they don’t want to host themselves nor, if they’re sharp, will they want to co-lo (co-lo makes sense if you’ve got some exiting servers but outside of that condition it’s probably not a factor). Additionally, most will be looking for either shared or dedicated hosting.

Now, if you simply Google something like “web host comparison” you’ll often get sites that may look legitimate but under the covers are marketing masquerading as a real site. Just be careful where you step. Here are a couple of lists with less vendor affiliation and more comparison of services:
http://webhost.thelist.com/
http://www.websitehostdirectory.com/

For those looking to host applications, more than sites, and particularly if you’d like to do this at not cost, check out:
http://en.wikipedia.org/wiki/Comparison_of_free_software_hosting_facilities

So much for the high notes. I hope to get a chance to address hosting in a low-end vs. high-end comparison in the future. For now, I hope this helps.