|
|
INTERNET ACCESS
Choose the Right ISP for Your E-Business
These tips will help you get it right when you go to choose an ISP for your business -- from getting started and technical concerns to making sure you get solid support.
By Brent Seely
When setting up or growing an e-business, most companies spend a lot of energy and diligence setting up the architecture: acquiring enough servers, hooking up a big enough pipe, choosing the right software technologies, developing the applications, and creating a compelling site design with an intuitive user interface. They spend hours researching and planning to fit these pieces into place. But when it comes to one of the most important decisions of all -- choosing the Internet Service Provider (ISP) that provides that vital link between us and the infrastructure of the Web -- many companies foolishly make the selection based on price alone. Because so many ISPs do position themselves based on price, it's easy to fall into that trap. However, there are several strategic factors essential to consider, including redundancy, reliability, scalability, and support. Because connectivity to the Web is the "spinal cord" of all things Web, choosing a good ISP can be the difference between e-business success and failure.
Know what you're comparing
The normal selection process of an ISP includes looking at a variety of very similar documents: network topography (both owned and partnered), data center maps, rack specifications, support models, and pricing grids. But don't let the paper deluge lull you into thinking you're comparing apples to apples. Although the end product is the same -- getting your site onto the information superhighway -- the roads your ISP takes to get there can be very different.
There are several tiers of service providers. The first tier of providers own their own infrastructure. These are companies such as Exodus, AboveNet, and Level3. A second tier provider is often a customer of the first tier providers and usually offers space and bandwidth only -- no additional services, such as monitoring, managed environments, or professional services. There is also the managed service provider (MSP) and/or application service provider (ASP), such as Loudcloud, Intira, and Resource Peak, which are smaller xSPs that rent space and bandwidth from the first tier. These providers usually offer additional services like Domino Hosting. Check out http://Advisor.com/article/chenb04 for more information on MSPs and ASPs.
The further down the chain you go, the price is generally less expensive. But be sure you are aware what services have been cut in exchange for the price savings. Some of these tradeoffs may be fine for your e-business; other features are mission-critical and non-negotiable for your business. Ask yourself if any of the following services are important to your business, then make sure your ISP provides those features:
- The data center and the network-operating center (NOC) is staffed 24x7x365. This way, you will at least be notified if something goes wrong.
- The staff on hand has the expertise in the particular areas your site needs, such as a networking or database administrator, Web traffic analyzer, NT or UNIX administrator, and is able to immediately handle issues such as rebooting a machine or other things you may not be able to do yourself remotely.
- Backup power and alternate sources of power in case the utility company can't provide power for an extended period of time. Remember, the Web is global, so your customers may not be aware there is a power outage in your area and will still try to access your site.
- Redundant equipment such as routers, switches, power supplies, and Web servers, so there's not a single point of failure. This may significantly add to your monthly charges, but balance this against what would happen if your site went down (and for how long it would be down) if a piece of equipment breaks and has to be ordered.
- High capacity, low utilization. To take into account spikes in usage, you want your provider to have a high amount of available capacity, but a low amount of utilization. In other words, you do not want a provider who, on any given day is using 75 percent of its ultimate capacity -- because one busy day on the Web could bring all its customers crashing down.
- Conservative loading of the electric network. If you've ever plugged a space heater in the same socket as a lamp, you know it's easy to overload a circuit. Ask how the ISP balances the ratio of equipment to power.
- A service level agreement (SLA) based on quantified standards such as network thresholds, response times, and specific remedies if the SLA is not met.
It's possible your site won't need all these features. Maybe your site is for internal use only, and doesn't have to run 24x7x365. Perhaps it's password protected and you can restrict the access so there won't be any spikes. Or maybe you're using the ISP for connectivity to the Web only and are running your own internal data center and do not need the services of the ISP's database and networking specialists.
For these situations, a smaller ISP may work for you -- they are often less expensive and can provide more flexible terms because they are eager to get your business. Just make sure they provide everything you need and that everything you expect is in writing, particularly in the SLA.
Dig into the technical specs
ISPs love to show you very detailed and colorful presentations about their network topography and bandwidth capacity as proof they are the market leader of all ISPs. They will take you on a tour to show off their data center and may even point out the huge "pipe" that connects to the Internet. Although this gives you a good sense of the facility and offerings, it does not address most of the technical issues vital to your success. It is important you have someone -- yourself, an employee, or a consultant -- ask the ISP representative several critical technical questions such as:
What server and network capacity can I run at with the current infrastructure?
If you are planning aggressive growth, based on the current number of hits, database transactions, and current storage, you want to look at running at 50 percent capacity for the systems in the current infrastructure. You'll have to have some idea of how many thousands of "hits" a month you're expecting and possibly how many database transactions occur during that time too. Also identify how much data storage you need now and if that stays constant. Adding drive capacity in most cases should not cause interruptions in service.
How do I dynamically scale to accommodate traffic spikes?
If you are able to keep your systems running at 50 percent capacity, you can probably grow to about 75 percent without too much noticeable degradation. If the spikes may be higher than a 25 percent increase, the ISP should be able to install additional load balancers or servers to clusters rather quickly.
What failover or high availability (HA) mechanisms do you employ for servers, networking equipment, and data storage?
These are essential components of your overall Web architecture, so make sure the ISP has plans for both an immediate solution if a piece of equipment fails, and a replacement or repair plan.
For servers and networking equipment, ISPs should employ load sharing and/or hot-standbys. In load sharing, all the servers are being used. If one goes down, the load on the others is evenly distributed, with some performance degradation. With hot-standbys, one server does all the work; but if it fails, the other system takes over automatically. This means more upfront costs, but when a failure occurs, you are protected.
Data storage should have some sort of Redundant Arrays of Inexpensive Disks (RAID) implementation, such as RAID 4, 5, or even simple disk mirroring. This protects against loss of data if a disk crashes. Servers themselves should have some sort of mirroring, so if one disk drive fails, it doesn't bring down the server.
Don't forget that high availability usually means eliminating single points of failure, even for the "little things" such as power supplies, Network Interface Cards (NICs), and single disk drives. Find out whether your ISP takes these things into account.
In the case of an immediate problem, you need to repair or replace the failed component for longer-term security. You wouldn't drive a thousand miles on your spare tire; the same holds true for your Web infrastructure. Find out if your ISP has spare parts and staff available; in which case you can return to normal operations quickly. Otherwise, replacement hardware will have to be ordered, which could mean a delay of 24 to 48 hours, or longer. Ask if your ISP keeps spare equipment on site, and if not, how close is the supplier and what is the delivery time?
How do I ensure price protection so I'm only paying for the bandwidth I'm using? How do I avoid paying premium pricing for traffic spikes?
Typically, you pay for an agreed upon amount of bandwidth per month, with penalty charges for going over that amount. There are several issues here: first, ask them how they measure bandwidth. Then find out how they charge for overages. Is it for the actual amount you went over, or is it rounded up to the next level of bandwidth you can purchase? Be sure to find out if you can scale up your bandwidth for a set period of time to handle expected surges in your e-business. For example, you may expect a "flash crowd" for the first week after you offer a new product online. Will you be able to purchase the necessary bandwidth ahead of time, or are you going to pay for the overage in penalty charges?
What kind of uptime guarantee does the ISP provide?
Be sure you understand what is meant by "uptime." Is it for the backbone connection only, the network and operating system, or are you in a managed environment which guarantees uptime for connection, network, servers, and applications? Typically, there are "scheduled downtimes" for maintenance or upgrades, for example. Make sure these scheduled maintenance windows occur at a time compatible with your typical site traffic.
Uptime is generally expressed in what are called "nines." For example "five nines" is 99.999 percent. This level of uptime means your site is down for just over five minutes total in an entire year. Three nines, or 99.9 percent means your site could be down for up to eight hours in one year's time.
Typical exceptions to uptime include "acts of God" such as earthquakes, hurricanes, and flood, and may also include long-term general power outages (such as the rolling blackouts California experienced this past winter).
What are the ISP's peering arrangements?
This is an agreement between two or more ISPs to exchange traffic. The exchange can happen over public exchange points or via private peering. Public exchange points are often congested, while private peering is usually more direct and faster. If your target audience can be loosely classified as a typical home user with a dial-up account, you may want to ask if your ISP peers with public exchange points such as AOL and Earthlink. If corporate users are your target audience, you may want to check if the ISP peers with some of the larger dedicated-circuit-centric ISPs like Verio, UUNet, and BBN Planet. Some ISPs may not disclose their peering arrangements in detail, but most are willing to give you at least some idea of who they peer with and how saturated the links are. Avoid the ISPs that claim to peer with "everyone," and the ones who won't disclose any information on their peering arrangements.
Do you have existing customers who are running sites of about the same volume/transactions as mine whom I can call?
While this isn't a technical question, talking to existing customers of similar size can give you tremendous insight as to whether this ISP is appropriate for your particular business needs.
The answers to these questions will provide you with a clear, concise picture of not only whether the ISP can meet your needs today, but if it will be able to handle your future growth.
Get specifics about support
Many ISPs say they offer 24x7x365 support, but in this industry, "support" can mean many different things. Ask questions to ascertain what you are really getting:
Who manages the environment, and down to what layer? How much administration access do you have to your data? Can you (or someone you outsource to) directly administer your server to make sure your server software is running and running optimally?
Typically, if your provider sells you a "managed" environment, it takes the responsibility for keeping the operating system and servers running, and also that it is the only one that can make changes to the operating system or equipment. This is great if you don't want the responsibility of managing the Web environment or don't have the staff to do so 24x7x365, but it also means you give up a little bit of control. On the other hand, if you are not in a managed environment, you have more control, but all the responsibility. In that situation, the ISP's responsibility stops at the network backbone.
What type of "system health" monitoring tools does the ISP offer? Can the technology discern between hardware/software problems?
There are many small pieces to the overall big picture of hosting a Web site. When there is a problem, it's critical to know where to begin to look. You might want to start with the connection to the Internet and work your way backward to the individual server. Does the ISP have a way of telling you if the site is down due to a bandwidth or overall network problem? Does it send "dummy transactions" to your database, application, and Web servers on a regular (typically every five minutes) basis to make sure the software is still working? Does it "ping" the hardware every minute to make sure all the equipment is still functioning? Most of the time, you won't look at these statistics -- but when something goes wrong, you'll be glad the information is available!
What kind of intrusion detection and response services does the ISP offer?
This is definitely an area where you get what you pay for. Find out if the company just monitors and reports, or if it has a specific security team that actively responds to a perceived intrusion. Also ask if it recommends security patches and updates as it discovers them, or if that is your responsibility.
What kind of access does the ISP have to the building? Can you get to the hardware (if needed)? If not, how long is the guaranteed response time?
If your ISP is also hosting your equipment, be sure you know what your access rights are. Is your equipment in its own cage, or part of a bank of servers shared by many customers? If something goes wrong, can you get into the building? Will you be able to get into the cage? Will you be able to get to your equipment? If you don't have 24x7x365 access, who does? If you are in a "lights out" center, where you have no physical access to your equipment, how long will it take to get someone to make the necessary changes? Look at the answers to all these questions two ways: How easily can I reach my equipment, and how well are unauthorized people kept away from my equipment?
Is my data backed up or just the server's operating system? How often? What types of media are used and are they stored offsite? How quickly can restoration from backup be done? Is it a hot backup or does my database application need to shut down to be backed up?
Incremental backups of customer data are usually done nightly, with a full backup taken about once a week and stored offsite. Backups are generally written to tape, such as AIT or DLT. Restores from backup tapes usually take about 48 hours. Usually the servers can be up and running during backups, though they may take a slight performance hit, so backups are generally scheduled for the middle of night, (though on the Internet, it's always 9 a.m. somewhere).
How often does the company verify backup integrity?
Backup integrity is a procedure that verifies the backup and restore process actually works. A random sampling of the backup (for example, a single tape), is picked and a restore is attempted. If this is successful, you can be sure your regularly scheduled backups will do what you expect should the worst happen. A major data loss is the wrong time to find out your backup process isn't grabbing all the necessary files, or the restore isn't able to push the correct files back out. Backup integrity is usually verified about once a month, which is frequent enough to be safe, but not so frequently as to waste time or staff time.
Where does the ISP's responsibility end and your company's begin if there are problems?
It is extremely important both you and the ISP are clear on the line of demarcation. This eliminates the possibility of critical functions falling into the cracks, and finger pointing should something fail. Having this documented can save you tens of thousands of dollars, and give you peace of mind.
Caveat emptor -- avoid these common pitfalls
When comparing prices, know exactly what you're giving up. Beware of the following "cost-cutting" measures that can compromise your site:
- Not manning the network operations center (NOC), data center, and support center 24x7x365.
- No generators or backup power.
- Lack of failover equipment and hot spares for equipment.
- Liberal down-time policies.
- Undefined or extended response times for problem resolution.
- Using desktop boxes rather than servers for mission-critical operations. Additionally, look for systems manufactured by a reputable company.
- Non-redundant or offbrand networking equipment, including firewalls.
- Overutilization of shared network pipes. Anything above 50 percent capacity should make you look twice.
- Excessive "hops" to the Internet backbone. For example: The ISP may have an OC12 pipe, but it may be connected to another ISP with a T3 ring and then out to the backbone, which will be less capacity/slower than having the pipe connected directly (or short hop) to the backbone.
Choose your partner well
As the mix of ISPs' customer base moves away from dot-coms and toward non-high-tech enterprise customers, the Web hosting industry is moving toward managed environments because these customers are less likely to have the staff or equipment to manage Web sites and don't want to stray from their core competencies. You can expect to see two different paths of managed environments: standardized "cookie cutter" hosting environments that ensure uptime by leveraging best-of-breed equipment and best practices in management over and over again; or highly customized managed environments that meet each business's specific needs but reduce risk through rigorous testing and qualification processes. Web hosting companies are trying to move away from being strictly co-location providers and more toward turnkey professional services organizations.
Pricing has not really dropped, because as online customers have demanded better and more consistent performance, ISPs have engineered more safeguards such as redundant hardware, increasing costs. While component pricing may drop over time, the cost of increased and improved services will also be reflected in your monthly recurring charges.
Just as a power outage can halt business for a brick and mortar store, any site failure can make a significant impact on your bottom line, and sometimes, even your reputation. Choosing the right ISP is a crucial element in your e-business strategy. It affects everything in the e-business ecosystem: from connect time to outages. You may choose and invest in the best technology (software, development, hardware), but unless it is supported by the equivalent ISP, it's all for naught. Calculate, be cautious, inquisitive, and diligent.
Brent Seely is president and CEO of Resource Peak, a Fremont, California, company that specializes in Notes and Domino application development and deployment, including Domino hosting, infrastructures, and applications. http://www.resourcepeak.com
Keyword Tags: Business Technology, e-Business Management, Infrastructure, Internet Operations, Internet Service Provider (ISP), Management, Resource Peak, Service, Support & Help, Technology Management, Web Operations, Web Services
ADVISORAMA Events in the past may be roughly divided into those which probably never happened and those which do not matter. -- William Ralph Inge
|
ARTICLE INFO
Print Edition: April/May 2001, Page 1
FREE ACCESS
|
SUBSCRIPTION STATUSYou are not signed-in. If you are a subscriber to this publication, sign-in above to access locked articles. To subscribe or renew go to www.AdvisorStore.com.
|

Get it all -- every current and past ADVISOR tech/business publication, now all-in-one subscription, with new articles and a huge reference library packed with expert advice, how-to and downloads. Subscribe now to get it all.![]() 
Read the advanced guide to creating custom business database solutions with FileMaker software. Subscribe now to gain access to all the archives and downloads.![]() 
Learn the fundamentals of using FileMaker Pro software. Every issue gives you step-by-step instructions on creating the databases you need. Subscribe now!![]()
![]()
![]()
 ![]()

Submit your tips, techniques and advice and let Advisor promote your business and build your career. Show the world what you know!![]()  ![]()
|
|