Synchronization of transactional data and analytical data between data centers

• US 9,443,087 B2
• Filed: 03/08/2013
• Issued: 09/13/2016
• Est. Priority Date: 03/08/2013
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Apigee Corporation (Alphabet Inc.)
• Inventors: Muguda, Naveenkumar
• Primary Examiner(s): Uddin, Md. I
• Application Number:
  US13/789,697
• Publication Number:
  US 20140258227A1
• Time in Patent Office: 1,285 Days
• Field of Search: 707/607, 707/620, 707/624
• US Class Current: 1/1
• CPC Class Codes: G06F 17/40 Data acquisition and logging for input to computer G06F3/00
• CPC Class Codes: G06F 21/60 Protecting data
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 2221/2101 Auditing as a secondary aspect
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management

Abstract

Synchronization of transactional data and analytical data between data centers. Metadata is received by a transactional system from a user interface included in a customer data center. The metadata is then forwarded from the customer data center to an analytical system in a master data center. Data is forwarded from the customer data center to the master data center, the data being encrypted with a key uniquely associated with a customer. Role creation calls to create roles for one or more users associated with the customer data center are subsequently detected. The role creation calls crossing a data center boundary are further masqueraded.

Claims

1. A method of synchronizing transactional data and analytical data between data centers, the method comprising:

receiving metadata by a transactional sniffer system from a user interface comprised in a customer data center to create and update the transactional data;

receiving in a first ephemeral data storage unit the transactional data from a transactional system;

forwarding the metadata from the customer data center to an analytical system in a master data center, wherein the analytical system manage analytical data including numerical values, metrics, and measurements;

forwarding data from the customer data center to the master data center, wherein the data is encrypted with a key uniquely associated with a customer;

detecting role creation calls by a user management sniffer system to create roles for one or more users associated with the customer data center;

authenticating one or more metadata calls in the customer data center;

masquerading the metadata calls, and other role sensitive calls crossing the data center boundary;

subsequent to the authenticating, masquerading the role creation calls crossing a data center boundary;

routing traffic from the customer data center to the master data center by an analytical proxy unit;

managing user credentials of one or more users associated with the customer data center by a first user management unit;

receiving the transactional data from the data forwarder unit for synchronizing the transactional data and the analytical data;

receiving the transactional data from the transactional system in a second ephemeral data storage unit;

enabling remote resetting of the user credentials by a credential management interface unit; and

managing the one or more users by a second user management unit.

2. The method as claimed in claim 1, wherein forwarding the metadata comprises:

storing the metadata in the master data center.

3. The method as claimed in claim 1, wherein forwarding the data comprises:

storing the data in the customer data center.

4. The method of claim 1 and further comprising

managing user credentials of the one or more users associated with the customer data center.

5. The method of claim 4 and further comprising

enabling remote resetting of the user credentials of the one or more users by the master data center.

6. A multi data center system for synchronizing transactional data and analytical data, the multi data center system comprising:

a customer data center comprising;

one or more processor;

a transactional system to create and update transactional data;

a user interface unit that receives metadata;

a transactional sniffer unit that detects the metadata;

a first ephemeral data storage unit that receives the transactional data from the transactional system;

a data forwarder unit that forwards the transactional data to a master data center wherein the transactional data is encrypted with a key uniquely associated with the customer;

a metadata store that stores the metadata and the transactional data;

an authenticator for authenticating one or more metadata calls in the customer data center;

a role masquerader unit that (i) masquerades the metadata calls, and other role sensitive calls crossing the data center boundary, and that (ii) masquerades role creation calls crossing a data center boundary subsequent to the authenticating;

an analytical proxy unit that implements an interface and routes traffic from the customer data center to the master data center;

a first user management unit that manages user credentials of one or more users associated with the customer data center; and

a user management sniffer unit that detects role creation calls to create roles for the one or more users associated with the customer data center; and

the master data center comprising;

an analytical system that deals with analytical data wherein the analytical data includes numerical values, metrics, and measurements;

a metadata receiver that receives the metadata from the transactional sniffer unit;

a metadata storage unit that stores the metadata;

a data receiver unit that receives the transactional data from the data forwarder unit for synchronizing the transactional data and the analytical data;

a second ephemeral data storage unit that receives data from the transactional system;

a credential management interface unit that enables remote resetting of the user credentials; and

a second user management unit that manages the one or more users.

7. The multi data center system as claimed in claim 6, wherein the user interface unit further initiates queries that need to be serviced by the analytical system and the data forwarder unit.

8. The multi data center system as claimed in claim 6, wherein the first ephemeral data storage unit encrypts the data with a key uniquely associated with a customer.

9. A computer program product stored on a non-transitory computer-readable medium that when executed by a processor, performs a method of synchronizing transactional data and analytical data between data centers, comprising:

receiving metadata by a transactional system from a user interface comprised in a customer data center to create and update the transactional data;

receiving in a first ephemeral data storage unit the transactional data from a transactional system;

forwarding the metadata from the customer data center to an analytical system in a master data center, wherein the analytical system manages analytical data including numerical values, metrics, and measurements;

forwarding data from the customer data center to the master data center, wherein the data is encrypted with a key uniquely associated with a customer;

detecting role creation calls to create roles for one or more users associated with the customer data center;

authenticating one or more metadata calls in the customer data center;

masquerading the metadata calls, and other role sensitive calls crossing the data center boundary;

subsequent to the authenticating, masquerading the role creation calls crossing a data center boundary;

routing traffic from the customer data center to the master data center by an analytical proxy unit;

managing user credentials of one or more users associated with the customer data center by a first user management unit;

receiving the transactional data from the data forwarder unit for synchronizing the transactional data and the analytical data;

receiving the transactional data from the transactional system in a second ephemeral data storage unit;

enabling remote resetting of the user credentials by a credential management interface unit; and

managing the one or more users by a second user management unit.

10. The computer program product as claimed in claim 9, wherein forwarding the metadata comprises:

storing the metadata in the master data center.

11. The computer program product as claimed in claim 9, wherein forwarding the data comprises:

storing the data in the customer data center.

12. The computer program product of claim 9 and further comprising

managing user credentials of the one or more users associated with the customer data center.

13. The computer program product of claim 12 and further comprising

enabling remote resetting of the user credentials of the one or more users by the master data center.