Abstract: Creating and executing a distributed stream processing operator graph based on a query. The operator graph includes movable stream algebra operators for processing events received from high volume data streams. The operators are partially compiled and distributed to computing devices for completion of the compilation and subsequent execution. During execution, the operators maintain minimal state information associated with received events via an expiration time assigned to each of the event instances. Additional events are generated and aggregated by the operators for communication to a service responsible for the query.

Abstract: A distributed event processing system that can organize (e.g., order) input streams regardless of actual time of receipt is provided. This order may simply be arrival order or given explicitly on a specific event attribute, such as a timestamp or sequence number. Traditional standing event queries, such as a temporal correlation of events across multiple streams, often block if an input stream is slow or may produce an incorrect answer if events fail to arrive within the fixed time interval. In response to this situation, the subject innovation employs punctuation and heartbeats in connection with a robust and scalable event processing system. The innovation discloses mechanisms by which heartbeats and timestamps can be regularly generated by low-level nodes (e.g., sources) and propagated through the network, to unblock standing event pattern queries and align events from multiple distributed streams.

Abstract: Event data associated with state data corresponding to an instance of a process is collected by an interceptor associated with a server that performs an operation to modify the state data. The server performs a single transaction with the database to store both the modified state data and the associated event data, the transaction either succeeding or failing, whereby if the transaction succeeds, then both the state data and the event data are stored at the database, and if the transaction fails, then both the state data and the event data are not stored at the database. The event data stored at the database is then transmitted to a tracking service for conversion into a query-able format.

Abstract: In a method and system for debugging a program, a debugging module is loaded into a normal thread of execution of the program. A user may then send commands to the debugger module from a command console module operating in a safe separate process. The debugger module receives the commands and converts them into function calls to objects that are accessible by the program. This allows the user to interact manually with the objects and achieve substantially the same responses from the objects as the program itself would have obtained during its normal execution. Thus the user can effectively debug the program without having to know the internal structure of any of its constituent objects.

Abstract: An extension of object-oriented programming languages enables the use of replaceable classes and virtual constructors, thereby allowing existing code that creates objects of a base class to be reusable for creating instances of a new class derived from the base class. A base class intended to be replaceable later is declared to be replaceable. In the case of a compiled language, the programming code defining and using the base class is compiled into a reusable module. Later, a new class derived from the base class is identified as a replacement for the base class and is used in new programming code that uses the existing reusable module. The replacement relationship between the old base class and the new class is registered. During execution of the program, when the old code of the reusable module indicates the creation of an object of the base class, the registered replacement information is referenced.

Abstract: Event data associated with state data corresponding to an instance of a process is collected by an interceptor associated with a server that performs an operation to modify the state data. The server performs a single transaction with the database to store both the modified state data and the associated event data, the transaction either succeeding or failing, whereby if the transaction succeeds, then both the state data and the event data are stored at the database, and if the transaction fails, then both the state data and the event data are not stored at the database. The event data stored at the database is then transmitted to a tracking service for conversion into a query-able format.