Method and system for implementing a digital application architecture with distinct processing lanes

• US 9,652,341 B1
• Filed: 12/12/2014
• Issued: 05/16/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): Schell, Joseph
• Application Number:
  US14/568,780
• Time in Patent Office: 886 Days
• 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
• 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 digital application architecture comprising: a first co-location comprising: a first pod that supports a first subset of users; the first pod comprising a plurality of designated processing lanes, where a first processing lane supports a first business function, a second processing lane supports a second business function; and a third processing lane supports a third remote business function across a network; a second pod that supports a second subset of users; and a failover pod that supports one or more other pods from a second co-location; and an enterprise that replicates data for the first subset of users and the second subset of users and transmits the replicated data to the first co-location.

Claims

1. A system having a network architecture, the system comprising:

a first co-location comprising;

a first pod comprising a processor that supports a first subset of customers associated with an entity;

the first pod comprising;

a web browser comprising a plurality of sections, each section corresponds to a designated processing lane;

a plurality of designated processing lanes, where a first designated processing lane supports a read local function that accesses and displays customer account information for a customer, the read local function is limited to accessing a read local database, a second designated processing lane supports a write local function that records performance data associated with the customer, the write local function is limited to accessing a write local database and the read local database; and

a third designated processing lane supports a third remote business function across a network that sends process data to an enterprise center for processing;

wherein the designated processing lanes are distributed based on the customer'"'"'s personal usage and interaction with the entity;

a second pod comprising a processor that supports a second subset of customers associated with the entity; and

a failover pod comprising a processor that supports one or more other pods in a second co-location and one or more other pods in a third co-location during a failover mode; and

an enterprise datacenter that replicates data for the first subset of customers and the second subset of customers and transmits the replicated data for the first subset of customers and the second subset of customers to the first co-location.

2. The system of claim 1, wherein the first designated processing lane supports a read local function.

3. The system of claim 2, wherein the second designated processing lane supports a read local function.

4. The system of claim 1, wherein the third designated processing lane supports a read remote function wherein the read remote function is performed over the network.

5. The system of claim 1, wherein the plurality of designated processing lanes further comprises a fourth designated processing lane that supports a write remote function, wherein the write remote function is performed over the network.

6. The system of claim 1, wherein the first pod provides a user interface to the first set of users, the user interface comprises a plurality of segments.

7. The system of claim 6, wherein each segment corresponds to one of the plurality of designated processing lanes.

8. The system of claim 6, wherein a first segment corresponds to one of the plurality of designated processing lanes, the first segment comprising a sub-segment that corresponds to another one of the plurality of designated processing lanes.

9. The system of claim 1, wherein the first co-location comprises a third pod that supports a third subset of users.

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

implementing a first co-location comprising;

a first pod comprising a processor that supports a first subset of customers associated with an entity;

the first pod comprising;

a web browser comprising a plurality of sections, each section corresponds to a designated processing lane;

a plurality of designated processing lanes, where a first designated processing lane supports a read local function that accesses and displays customer account information for a customer, the read local function is limited to accessing a read local database, a second designated processing lane supports a write local function that records performance data associated with the customer, the write local function is limited to accessing a write local database and the read local database; and

a third designated processing lane supports a third remote business function across a network that sends process data to an enterprise center for processing;

wherein the designated processing lanes are distributed based on the customer'"'"'s personal usage and interaction with the entity;

a second pod comprising a processor that supports a second subset of customers associated with the entity; and

a failover pod comprising a processor that supports one or more other pods in a second co-location and one or more other pods in a third co-location during a failover mode; and

receiving replicated data at the first co-location, from an enterprise datacenter, wherein the replicated data is for the first subset of customers and the second subset of customers.

11. The method of claim 10, wherein the first designated processing lane supports a read local function.

12. The method of claim 11, wherein the second designated processing lane supports a read local function.

13. The method of claim 10, wherein the third designated processing lane supports a read remote function wherein the read remote function is performed over the network.

14. The method of claim 10, wherein the plurality of designated processing lanes further comprises a fourth designated processing lane that supports a write remote function, wherein the write remote function is performed over the network.

15. The method of claim 10, wherein the first pod provides a user interface to the first set of users, the user interface comprises a plurality of segments.

16. The method of claim 15, wherein each segment corresponds to one of the plurality of designated processing lanes.

17. The method of claim 15, wherein a first segment corresponds to one of the plurality of designated processing lanes, the first segment comprising a sub-segment that corresponds to another one of the plurality of designated processing lanes.

18. The method of claim 10, wherein the first co-location comprises a third pod that supports a third subset of users.