METHODS AND DEVICES FOR DETECTING SERVICE FAILURES AND MAINTAINING COMPUTING SERVICES USING A RESILIENT INTELLIGENT CLIENT COMPUTER

• US 20110047413A1
• Filed: 08/20/2010
• Published: 02/24/2011
• Est. Priority Date: 08/20/2009
• Status: Abandoned Application

• Current Assignee: Landmark Technology Partners Incorporated
• Original Assignee: Landmark Technology Partners Incorporated
• Inventors: McGILL, Robert E., Tsinman, Igor
• Application Number:
  US12/860,343
• Publication Number:
  US 20110047413A1
• Time in Patent Office: Days
• US Class Current: 714/15
• CPC Class Codes: G06F 11/1443 Transmit or communication errors
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 11/1662 the resynchronized component or unit being a persistent storage device re-synchronization of failed mirror storage G06F11/2082; rebuild or reconstruction of parity RAID storage G06F11/1008
• CPC Class Codes: G06F 11/2002 where interconnections or communication control functionality are redundant flexible arrangements for bus networks involving redundancy H04L12/40176
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2041 with more than one idle spare processing component
• CPC Class Codes: G06F 11/2048 where the redundant components share neither address space nor persistent storage
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 2201/855 Details of asynchronous mirroring using a journal to transfer not-yet-mirrored changes
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

Intelligent client computing devices track and record the changes they make to data, applications, and services. Systems, devices, and computer readable media for detecting service tier failures and maintaining application services provide a resilient client architecture that allows a client application on an intelligent client to automatically detect the unavailability of server tiers or sites and re-route requests and updates to secondary sites to maintain application services at the client tier in a manner that is transparent to a user. The resilient client architecture understands the level of currentness of secondary sites in order to select the best secondary site and to automatically and transparently bring this secondary site up to date to ensure no data updates are missing from the secondary site.

Claims

1. A computer-implemented resilient client failover method to maintain an up-to-date shared application service, the method comprising:

determining, with an intelligent client computer, a level of currentness of a primary site;

detecting, with the intelligent client computer, that the primary site is unavailable;

assessing, with the intelligent client computer, a level of currentness of a secondary site;

determining, with the intelligent client computer, updates made by the intelligent client computer to data for updating the primary site; and

replaying, by the intelligent client computer, the updates to the data made by the intelligent client computer to the secondary site.

2. The method of claim 1 further comprising:

establishing a time standard between the primary site and the secondary site to determine the data currentness of the secondary site.

3. The method of claim 1, wherein the primary site includes at least one of a web server, an application server, or a database server.

4. The method of claim 1, wherein the secondary site includes at least one of a web server, an application server, or a database server.

5. The method of claim 1, wherein the updates to data include at least one of a client request, an application service request, or an update to a data field.

6. The method of claim 1, wherein assessing the data currentness of the secondary site includes determining the most recent time synchronization of the secondary site.

7. The method of claim 1, wherein the data currentness is determined by the date and time of a most recent successful update to a persistent data store on the primary site.

8. The method of claim 1 further comprising:

storing the updates to data made by the intelligent client in a transaction log of the intelligent client.

9. The method of claim 8, wherein the updates replayed to the secondary site are performed prior to posting transactions or performing read operations on the secondary site.

10. The method of claim 1, wherein the primary site and the secondary site reside in the same computing device.

11. The method of claim 1, wherein the primary site and the secondary site reside in separate computing devices.

12. The method of claim 1, wherein replaying the updates to the secondary site further comprises:

tracking the updates in an application service routing table of the intelligent client to determine the primary site and at least one eligible secondary site; and

rerouting client updates to a secondary site.

13. The method of claim 12, wherein the secondary site receiving the rerouted client updates is selected based upon at least one of data currentness of eligible secondary sites, network traffic characteristics, and network capacity.

14. The method of claim 1, wherein detecting that the primary site is unavailable includes at least one of detecting a service tier failure, an application tier failure, or a database failure.

15. The method of claim 1 further comprising:

requesting, by the intelligent client computer, transaction services from a client object factory;

serializing as a transaction, by the client object factory, updates made by the intelligent client computer to data for updating the primary site;

storing the updates made by the intelligent client computer as the transaction in a transaction log; and

replaying the transaction to the secondary site when the intelligent client computer determines that the primary site is unavailable.

16. A computer readable storage media for maintaining an up-to-date shared application service, the computer readable storage media comprising one or more computer-readable instructions configured to cause one or more computer processors to execute operations comprising:

determining, with an intelligent client computer, a level of currentness of a primary site;

detecting, with the intelligent client computer, that the primary site is unavailable;

assessing, with the intelligent client computer, a level of currentness of a secondary site;

determining, with the intelligent client computer, updates made by the intelligent client computer to data for updating the primary site; and

replaying, by the intelligent client computer, the updates to the data made by the intelligent client computer to the secondary site.

17. The computer readable storage media of claim 16 further comprising computer-readable instructions configured to cause one or more computer processors to execute the operations comprising:

storing the updates to data made by the intelligent client in a transaction log of the intelligent client.

18. The computer readable storage media of claim 16, wherein the computer-readable instructions configured to cause one or more computer processors to execute the operations for replaying the updates to the secondary site further comprises computer-readable instructions configured to cause one or more computer processors to execute the operations comprising:

tracking the updates in an application service routing table of the intelligent client to determine the primary site and at least one eligible secondary site; and

rerouting client updates to a secondary site.

19. The computer readable storage media of claim 16, wherein detecting that the primary site is unavailable includes at least one of detecting a service tier failure, an application tier failure, or a database failure.

20. The computer readable storage media of claim 16, further comprising computer-readable instructions configured to cause one or more computer processors to execute the operations comprising:

requesting, by the intelligent client computer, transaction services from a client object factory;

serializing as a transaction, by the client object factory, updates made by the intelligent client computer to data for updating the primary site;

storing the updates made by the intelligent client computer as the transaction in a transaction log; and

replaying the transaction to the secondary site when the intelligent client computer determines that the primary site is unavailable.

21. An intelligent client computer device configured to implement a resilient client failover to maintain an up-to-date shared application service, the intelligent client computer device comprising:

a client object factory configured to determine a level of currentness of a primary site; and

a link to a control console storing a latest copy of an application services routing table, the intelligent client computer device configured to detect that the primary site is unavailable by accessing the application services routing table;

wherein the client object factory is further configured to assess a level of currentness of a secondary site, determine updates made by the intelligent client computer to data for updating the primary site, and to replay the updates to the data made by the intelligent client computer to the secondary site.

22. The intelligent client computer device of claim 21, wherein the client object factory is further configured to store the updates to data made by the intelligent client computer device in a transaction log.

23. The intelligent client computer device of claim 21 further comprising:

an application service routing table configured to track the updates to determine the primary site and at least one eligible secondary site and to reroute the updates to a secondary site.

24. The intelligent client computer device of claim 21, wherein the control console is further configured to detect that the primary site is unavailable by detecting at least one of a service tier failure, an application tier failure, or a database failure.

25. The intelligent client computer device of claim 21, wherein the client object factory is further configured to:

serialize updates made by the intelligent client computer to data for updating the primary site as a transaction

store the updates made by the intelligent client computer as the transaction in a transaction log; and

replay the transaction to the secondary site when the control console determines that the primary site is unavailable.

26. A computer-implemented resilient client update method using an active secondary site, the method comprising:

determining, with an intelligent client computer, a level of currentness of a primary site;

determining, with the intelligent client computer, updates made by the intelligent client computer to data for updating the primary site;

synchronously posting, with the intelligent client computer, the updates made by the intelligent client to the primary site;

assessing, with the intelligent client computer, a level of currentness of a secondary site; and

asynchronously routing the updates to the data made by the intelligent client computer from the primary site to the secondary site.