|
Whitepaper Abstract
"What if the web goes down?" It's a common question when people investigate web-based solutions. Certainly, technology introduces different failure modes than traditional processes. This begs the question, "How reliable are web-based solutions when compared with their client-server counterparts?"
The short answer is that web-based dental software applications, properly hosted, will be about ten times more reliable. Let's now explore what drives this amazing reliability. We will also identify some actions that can mitigate the small risk associated with web availability.
Client-Server Vulnerabilities
Most client-server failures can trace their cause to two primary origins:
First, every hardware component found in the server is a potentially catastrophic failure point. If failure of a computer is a given, then the ideal solution is to create an architecture designed for it. Unfortunately, there is no such architecture available at a reasonable price for office based client-server systems.
Secondly, the client-server installation is put together using consumer grade equipment. Moreover, the server is typically placed in a less-than-suitable location. The risk of bumping, or spilling, or nudging, or moving is synonymous with the risk of failure.
Finally, when a client-server based system goes down, you will need to call your "IT pro" to come to the office and repair the server. Even with responsive service, you still are looking at hours; for typical service it can be days or longer.
The result of all these failures ends up as system downtime that is measured in hours per month or days per year. That quality of service is very costly and is far inferior to web-based systems.
Web-based Systems
Web based systems will typically have downtime that is measured in minutes per year. Here's why:
Redundant and fault tolerant architectures. Backup systems and secondary backup systems are in place to take over for a failed primary system.
Professionally housed, managed and maintained systems. With professionally managed web-based systems there is someone who is on guard all the time.
Hardware Maintenance. When the published service life of a component is up it will be replaced, even if it is technically "still working".
Hot swappable. The computer does not need to be turned off to replace a component. Pretty amazing stuff, but that's what you get with a redundant web-based architecture.
Controlled Environment. Sterile, humidity controlled environments are made perfect for the operation of computers.
So, what if the web does go down?
The most common method of protecting against a web access failure in a dental office is to bring in a redundant web access point, like a wireless network card. Many offices find that after many months or years of uninterrupted service, they choose to go without the redundant web access point.
If the internet goes down, your Internet Service Provider puts all available resources at the problem until service is restored. Because you are not alone, the problem is resolved much quicker and at less expense.
So, most offices find that although the internet does sometimes go down, it is so infrequent and of such short duration, that a backup internet access point isn't justified. Client-server system downtime is on the order of ten times as disruptive in both frequency and duration when compared with web-based solutions.
|