Abstract: A computing device manages a router. A manager engine is instantiated based on a manager engine definition and instantiates a manager ESPE based on a created manager ESP model. A router configuration file is created based on mapping information read from the manager configuration file that describes connectivity between an event publishing source and a source window of the manager ESPE. A router engine is instantiated based on the created router configuration file. A connector is started to receive an event based on the router configuration file. The event is received in the source window of the manager ESPE processed based on the manager ESP model. A third computing device is selected by the router engine based on a usage metric received from each window of a plurality of windows defined by a remote ESP model configured to further process the processed event when it is received.

Abstract: A computing device manages a router. A manager engine is instantiated based on a manager engine definition and instantiates a manager ESPE based on a created manager ESP model. A router configuration file is created based on mapping information read from the manager configuration file that describes connectivity between an event publishing source and a source window of the manager ESPE. A router engine is instantiated based on the created router configuration file. A connector is started to receive an event based on the router configuration file. The event is received in the source window of the manager ESPE processed based on the manager ESP model. A third computing device is selected by the router engine based on a usage metric received from each window of a plurality of windows defined by a remote ESP model configured to further process the processed event when it is received.

Abstract: A computing device manages a router to route events between a plurality of computing device based on a manager configuration file. A manager engine is instantiated based on a manager engine definition and instantiates a manager ESPE based on a created manager ESP model. A router configuration file is created based on mapping information read from the manager configuration file that describes connectivity between an event publishing source and a source window of the manager ESPE. A router engine is instantiated based on the created router configuration file. A connector is started to receive an event based on the router configuration file. The event is received in the source window of the manager ESPE defined by the manager ESP model and processed based on the manager ESP model. A third computing device is selected by the router engine. The processed event is published to the third computing device.

Abstract: A computing device manages a router to route events between a plurality of computing device based on a manager configuration file. A manager engine is instantiated based on a manager engine definition and instantiates a manager ESPE based on a created manager ESP model. A router configuration file is created based on mapping information read from the manager configuration file that describes connectivity between an event publishing source and a source window of the manager ESPE. A router engine is instantiated based on the created router configuration file. A connector is started to receive an event based on the router configuration file. The event is received in the source window of the manager ESPE defined by the manager ESP model and processed based on the manager ESP model. A third computing device is selected by the router engine. The processed event is published to the third computing device.

Abstract: A first computing device manages a cluster of event stream processing (ESP) engines (ESPEs). A local ESP model is created based on information read from a manager configuration file that includes first connection information to connect to the second computing device and second connection information to connect the third computing device. An ESPE is instantiated on the first computing device based on the created local ESP model. The event block object is received from the second computing device in a first source window of the instantiated ESPE. A remote ESP model is deployed to a remote third computing device. The manager configuration file includes an indicator of the remote ESP model. The third computing device to receive the processed event block object is selected. The processed event block object is published to a second source window defined by the remote ESP model deployed to the third computing device.

Abstract: A method of acknowledging receipt of an event block object is provided. First connection information for connecting to an event stream processing (ESP) engine executing at a first computing device is received. A first connection to the ESP engine is established using the received first connection information. Second connection information for connecting to a publishing client executing at a second computing device is received. A second connection to the publishing client is established using the received second connection information, wherein the first connection differs from the second connection. An event block object is received from the ESP engine using the established first connection, wherein the event block object includes a unique identifier for the event block object. Successful processing of the event block object is determined.

Abstract: A first computing device manages a cluster of event stream processing (ESP) engines (ESPEs). A local ESP model is created based on information read from a manager configuration file that includes first connection information to connect to the second computing device and second connection information to connect the third computing device. An ESPE is instantiated on the first computing device based on the created local ESP model. The event block object is received from the second computing device in a first source window of the instantiated ESPE. A remote ESP model is deployed to a remote third computing device. The manager configuration file includes an indicator of the remote ESP model. The third computing device to receive the processed event block object is selected. The processed event block object is published to a second source window defined by the remote ESP model deployed to the third computing device.

Abstract: In a system, a first status of a first ESP engine (ESPE) executing at a first computing device is determined as newly active; a last published event block object identifier is determined as an identifier uniquely identifying a last event block object published to an out-messaging network device; a next event block object having an event block object identifier greater than the determined last published event block object identifier is selected from a first computer-readable medium; and the selected next event block object is published to the out-messaging network device. A first event block object is received from a second ESPE executing at a second computing device. A first status of the second ESPE is determined as standby by the second computing device. The received first event block object is stored by the second computing device in a second non-transitory computer-readable medium.

Abstract: A method for dynamically modifying a database schema in a streaming database management system receives a new database schema, compares the new schema to an existing schema, identifies the differences between the new schema and the existing schema, and applies the identified differences to the database in a single transaction, thereby producing a database organized according to the new database schema.

Abstract: In a system, a first status of a first ESP engine (ESPE) executing at a first computing device is determined as newly active; a last published event block object identifier is determined as an identifier uniquely identifying a last event block object published to an out-messaging network device; a next event block object having an event block object identifier greater than the determined last published event block object identifier is selected from a first computer-readable medium; and the selected next event block object is published to the out-messaging network device. A first event block object is received from a second ESPE executing at a second computing device. A first status of the second ESPE is determined as standby by the second computing device. The received first event block object is stored by the second computing device in a second non-transitory computer-readable medium.

Abstract: In a computing device supporting a failover in an event stream processing (ESP) system, an event block object is received. A first status of the computing device as active or standby is determined. When the first status is active, a second status of the computing device as newly active or not newly active is determined. Newly active is determined when the computing device is switched from a standby to an active status. When the second status is newly active, a last published event block object identifier that uniquely identifies a last published event block object is determined. A next event block object is selected from a non-transitory computer-readable medium accessible by the computing device. The next event block object has an event block object identifier that is greater than the determined last published event block object identifier. The selected next event block object is published to an out-messaging network device.

Abstract: A method of acknowledging receipt of an event block object is provided. First connection information for connecting to an event stream processing (ESP) engine executing at a first computing device is received. A first connection to the ESP engine is established using the received first connection information. Second connection information for connecting to a publishing client executing at a second computing device is received. A second connection to the publishing client is established using the received second connection information, wherein the first connection differs from the second connection. An event block object is received from the ESP engine using the established first connection, wherein the event block object includes a unique identifier for the event block object. Successful processing of the event block object is determined.

Abstract: An event stream processing system includes a versioned data structure layered over a log-structured store. A first address handle points to a first version of data in the versioned data structure. A stream of data updates from a data source create a second version of data in the versioned data structure, addressed using a second address handle.

Abstract: An event stream processing system includes a versioned data structure layered over a log-structured store. A first address handle points to a first version of data in the versioned data structure. A stream of data updates from a data source create a second version of data in the versioned data structure, addressed using a second address handle.

Abstract: A method for dynamically modifying a database schema in a streaming database management system receives a new database schema, compares the new schema to an existing schema, identifies the differences between the new schema and the existing schema, and applies the identified differences to the database in a single transaction, thereby producing a database organized according to the new database schema.

Abstract: In general, in one aspect, the invention relates to a method for transaction processing. The method includes specifying metadata and storing the metadata. An index is created in response to the stored metadata. The method also includes receiving a transaction, generating an index log of changes to the index in response to the received transaction, and modifying the first index in response to the generated index log.

Abstract: In general, in one aspect, the invention relates to a method for transaction processing. The method includes specifying metadata and storing the metadata. An index is created in response to the stored metadata. The method also includes receiving a transaction, generating an index log of changes to the index in response to the received transaction, and modifying the first index in response to the generated index log.