# US 2017/0169058 A1 · Embedded event streaming to a transactional highly-available in-memory database

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0169058 A1
- Document ID: US20170169058A1
- Status: Published application
- Kind: A1
- Application number: 15/377,010
- Filed: 2016-12-13
- Published: 2017-06-15
- Earliest claimed: 2015-12-14
- Assignees: VoltDB, Inc.
- Applicants: VoltDB, Inc.
- Inventors: Stefano M. Santoro; Anish Khanzode; Ryan Betts
- Web page: https://patentgrep.com/patent/US20170169058A1

## CPC

- G06F 16/21: Design, administration or maintenance of databases
- G06F 11/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)}
- G06F 16/2386: {Bulk updating operations (data conversion details G06F16/258)}
- G06F 16/258: {Data format conversion from or to a database}
- G06F 11/2028: {eliminating a faulty processor or activating a spare}
- G06F 11/2038: {with a single idle spare processing component}
- G06F 2201/80: Database-specific techniques
- G06F 2201/82: Solving problems relating to consistency
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A real-time transaction processing system and method include the provision of a real-time transactional data store having an importer subsystem embedded therein. The importer subsystem is configured to connect directly to a real-time data source without using an intermediate subsystem. Events are received via the real-time data source at the importer subsystem, which transacts the events into the real-time transactional data store to create one or more records in the real-time transactional data store corresponding to the events.

## Claims

### Claim 1

A computer-implemented method comprising:
providing a real-time transactional data store comprising an importer subsystem embedded therein;
connecting directly the importer subsystem to a real-time data source without using an intermediate subsystem;
receiving a plurality of events at the importer subsystem via the real-time data source; and
transacting, by the importer subsystem, the events into the real-time transactional data store to create one or more records in the real-time transactional data store corresponding to the events.

### Claim 2 (depends on 1)

The method of claim 1, wherein the intermediate subsystem comprises at least one of a client application, third-party code, and a third-party connector.

### Claim 3 (depends on 1)

The method of claim 1, further comprising connecting directly the importer subsystem to a plurality of real-time data sources.

### Claim 4 (depends on 1)

The method of claim 1, wherein the importer subsystem processes each of the events individually and not in one or more batches.

### Claim 5 (depends on 1)

The method of claim 1, wherein the events are received from the real-time data source asynchronously.

### Claim 6 (depends on 1)

The method of claim 1, wherein the events are transacted into the real-time transactional data store asynchronously.

### Claim 7 (depends on 1)

The method of claim 1, wherein transacting the events further comprises transforming the events into a transactional format usable by the real-time data store.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
identifying a failure in the importer subsystem;
connecting to the real-time data source a failover importer embedded in the real-time transactional data store; and
receiving further events at the failover importer via the real-time data source.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
identifying a failure in the real-time data source;
connecting the importer subsystem to a failover real-time data source; and
receiving further events at the importer subsystem via the failover real-time data source.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
identifying a failure in the importer subsystem and the real-time data source;
connecting to a failover real-time data source a failover importer embedded in the real-time transactional data store; and
receiving further events at the failover importer via the failover real-time data source.

### Claim 11 (depends on 1)

The method of claim 1, wherein the real-time transactional data store comprises a plurality of data store nodes, each data store node having a channel configured to receive events for a particular topic on a particular partition of a real-time data source.

### Claim 12 (depends on 11)

The method of claim 11, further comprising moving a channel from a first one of the data store nodes to a second one of the data store nodes to recover from a failure.

### Claim 13

A real-time transaction processing system comprising:
a real-time transactional data store comprising an importer subsystem embedded therein and configured to connect directly to a real-time data source without using an intermediate subsystem;
at least one memory for storing computer-executable instructions; and
at least one processing unit for executing the instructions on the at least one memory, wherein execution of the instructions programs the at least one processing unit to perform operations comprising:
receiving a plurality of events at the importer subsystem via the real-time data source; and
transacting, by the importer subsystem, the events into the real-time transactional data store to create one or more records in the real-time transactional data store corresponding to the events.

### Claim 14 (depends on 13)

The system of claim 13, wherein the intermediate subsystem comprises at least one of a client application, third-party code, and a third-party connector.

### Claim 15 (depends on 13)

The system of claim 13, wherein the importer subsystem is configured to connect directly to a plurality of real-time data sources.

### Claim 16 (depends on 13)

The system of claim 13, wherein the importer subsystem processes the each of the events individually and not in one or more batches.

### Claim 17 (depends on 13)

The system of claim 13, wherein the events are received from the real-time data source asynchronously.

### Claim 18 (depends on 13)

The system of claim 13, wherein the events are transacted into the real-time transactional data store asynchronously.

### Claim 19 (depends on 13)

The system of claim 13, wherein transacting the events further comprises transforming the events into a transactional format usable by the real-time data store.

### Claim 20 (depends on 13)

The system of claim 13, wherein the operations further comprise:
identifying a failure in the importer subsystem;
connecting to the real-time data source a failover importer embedded in the real-time transactional data store; and
receiving further events at the failover importer via the real-time data source.

### Claim 21 (depends on 13)

The system of claim 13, wherein the operations further comprise:
identifying a failure in the real-time data source;
connecting the importer subsystem to a failover real-time data source; and
receiving further events at the importer subsystem via the failover real-time data source.

### Claim 22 (depends on 13)

The system of claim 13, wherein the operations further comprise:
identifying a failure in the importer subsystem and the real-time data source;
connecting to a failover real-time data source a failover importer embedded in the real-time transactional data store; and
receiving further events at the failover importer via the failover real-time data source.

### Claim 23 (depends on 13)

The system of claim 13, wherein the real-time transactional data store comprises a plurality of data store nodes, each data store node having a channel configured to receive events for a particular topic on a particular partition of a real-time data source.

### Claim 24 (depends on 23)

The system of claim 23, wherein the operations further comprise moving a channel from a first one of the data store nodes to a second one of the data store nodes to recover from a failure.
