Method and system for implementing a distributed digital application architecture

• US 9,612,925 B1
• Filed: 12/12/2014
• Issued: 04/04/2017
• Est. Priority Date: 12/12/2014
• Status: Active Grant

• Current Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Original Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Inventors: Lewis, Michael L., Romanelli, Richard J.
• Primary Examiner(s): Manoskey, Joseph D
• Application Number:
  US14/568,850
• Time in Patent Office: 844 Days
• Field of Search: 714 41, 714 411, 714 13, 714 43, 714 471
• CPC Class Codes: G06F 11/1658 Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit
• CPC Class Codes: G06F 11/2005 using redundant communication controllers
• CPC Class Codes: G06F 11/2007 using redundant communication media
• CPC Class Codes: G06F 11/202 where processing functionality is redundant redundant communication control functionality G06F11/2005, redundant storage control functionality G06F11/2089
• CPC Class Codes: G06F 11/2023 Failover techniques
• CPC Class Codes: G06F 11/203 using migration
• 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/2046 where the redundant components share persistent storage G06F11/2043 takes precedence
• CPC Class Codes: G06F 11/2048 where the redundant components share neither address space nor persistent storage
• CPC Class Codes: G06F 11/2056 by mirroring
• 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 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: G06F 2201/85 Active fault masking without idle spares active fault masking without idle spare hardware where processing functionality is redundant G06F11/2035
• CPC Class Codes: G06F 3/048 Interaction techniques based on graphical user interfaces [GUI]
• CPC Class Codes: G06Q 20/00 Payment architectures, schemes or protocols apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G07G 1/0009 Details of the software in the checkout register, electronic cash register [ECR] or point of sale terminal [POS]
• CPC Class Codes: H04L 67/1095 : Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/52 : specially adapted for the location of the user terminal
• CPC Class Codes: H04N 21/85 : Assembly of content; Generation of multimedia applications
• CPC Class Codes: H04N 21/8583 : by creating hot-spots

Abstract

According to an embodiment of the present invention, an automated computer implemented method and system for implementing a network architecture comprising: a first co-location comprising: a first pod that supports a first subset of users; a second pod that support a second subset of user; a first failover pod that supports one or more other pods from a second co-location and one or more other pods from a third co-location during failover mode; the second co-location comprising: a third pod that supports a third subset of users; a fourth pod that supports a fourth subset of users; a second failover pod that supports one or more other pods at the first co-location and one or more pods from another co-location during failover mode; and an enterprise entity that replicates data for each of the co-locations and communicates the replicated data to the first co-location and the second co-location.

Claims

1. A network architecture comprising:

a first co-location comprising;

a first pod that supports a first subset of users;

a second pod that support a second subset of user;

a first failover pod programmed to exclusively support one or more other pods from a second co-location and one or more other pods from a third co-location during failover mode, wherein the first failover pod stores replicated data from the second co-location and the third co-location;

the second co-location comprising;

a third pod that supports a third subset of users;

a fourth pod that supports a fourth subset of users;

a second failover pod programmed to exclusively support one or more other pods at the first co-location and one or more pods from another co-location during failover mode, wherein the second failover pod stores replicated data from the first co-location and the another co-location; and

an enterprise entity that replicates data for each of the co-locations and communicates the replicated data to the first co-location and the second co-location.

2. The system of claim 1, wherein the first subset of users is specific to a first geographic region associated with the first co-location.

3. The system of claim 1, wherein the second subset of users is specific to a second geographic region associated with the first co-location.

4. The system of claim 1, wherein the first failover pod receives inter-data replication from the one or more other pods at the first co-location.

5. The system of claim 4, wherein the second failover pod receives inter-data replication from the one or more pods from another co-location.

6. The system of claim 5, wherein during the failover mode, inter-data replication is suspended from the one or more pods from another co-location.

7. The system of claim 4, wherein during the failover mode, inter-data replication is suspended from the one or more other pods at the first co-location.

8. The system of claim 1, wherein the first pod comprises a plurality of designated processing lanes.

9. The system of claim 8, wherein the plurality of designated processing lanes comprises a first processing lane that supports local functions.

10. The system of claim 9, wherein the plurality of designated processing lanes comprises a second processing lane that supports remote functions.

11. A method for implementing a network architecture, the method comprising the steps of:

implementing a first co-location comprising;

a first pod that supports a first subset of users;

a second pod that support a second subset of user;

a first failover pod programmed to exclusively support one or more other pods from a second co-location and one or more other pods from a third co-location during failover mode, wherein the first failover pod stores replicated data from the second co-location and the third co-location;

the second co-location comprising;

a third pod that supports a third subset of users;

a fourth pod that supports a fourth subset of users;

a second failover pod programmed to exclusively support one or more other pods at the first co-location and one or more pods from another co-location during failover mode, wherein the second failover pod stores replicated data from the first co-location and the another co-location; and

receiving replicated data from an enterprise entity that replicates data for each of the co-locations and communicates the replicated data to the first co-location and the second co-location.

12. The method of claim 11, wherein the first subset of users is specific to a first geographic region associated with the first co-location.

13. The method of claim 11, wherein the second subset of users is specific to a second geographic region associated with the first co-location.

14. The method of claim 11, wherein the first failover pod receives inter-data replication from the one or more other pods at the first co-location.

15. The method of claim 14, wherein the second failover pod receives inter-data replication from the one or more pods from another co-location.

16. The method of claim 15, wherein during the failover mode, inter-data replication is suspended from the one or more pods from another co-location.

17. The method of claim 14, wherein during the failover mode, inter-data replication is suspended from the one or more other pods at the first co-location.

18. The method of claim 11, wherein the first pod comprises a plurality of designated processing lanes.

19. The method of claim 18, wherein the plurality of designated processing lanes comprises a first processing lane that supports local functions.

20. The method of claim 19, wherein the plurality of designated processing lanes comprises a second processing lane that supports remote functions.