| Device Healthcare - Decoupled Support |
![]() |
![]() |
![]() |
Give me liberty or give me death
However, none of these functions are necessary, or even important, for device support. In addition, each function is also implemented locally and cached on the device, and the cache can be synchronized with the server if it ever becomes available. The same databases, with the same schema, exist on both the server and the local client. The local client implements them with a fast and efficient lightweight database engine, since it does not need to service multiple database clients. In this way, the devices cooperate with each other to manage distribution among themselves. This means that the devices can operate with all of the server functions even if they never have access to the server, as long as they have intermittent access to each other, and at least one device has intermittent access to the server. BenefitThe biggest benefit of Decoupled Support for a support organization is the strong support of mobile devices. There are other reasons why Device Healthcare is particularly well suited for mobile device support, but Decoupled Support is the most important one. The other major benefit is the freedom from a critical central resource. Even if a server is down in the Device Healthcare paradigm, there is no serious service degradation. The devices go on working by themselves, and when the server becomes available again, the synchronization catches up and things continue normally. UniquenessThis is very simple. For any other offering, ask to see how it can run and perform all its functions without ever having a connection to a server. If it can't, then it doesn't have Decoupled Support, and it will always have trouble supporting truly mobile devices. Return To Top
|