Method and system for implementing a distributed digital application architecture

Patent metadata

Field	Value
Publication number	US-9612925-B1
Application number	US-201414568850-A
Country	US
Kind code	B1
Filing date	Dec 12, 2014
Priority date	Dec 12, 2014
Publication date	Apr 4, 2017
Grant date	Apr 4, 2017

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.

First claim

What is claimed is:

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.

Assignees

• Jpmorgan Chase Bank Na

Inventors

• Lewis Michael L
• Romanelli Richard J

Classifications

• G06F11/2056

  by mirroring · CPC title

• G06F11/2023

  Failover techniques · CPC title

• G06F11/2007 Primary

  using redundant communication media · CPC title

• G06F2201/85

  Active fault masking without idle spares · CPC title

• H04L67/52

  specially adapted for the location of the user terminal · CPC title