Abstract: A network device includes a database that includes database entries, an external data that includes external data entries, an interpreter, and a standing query instance (SQI). The interpreter is programmed to convert an external data entry into a temporary database entry and provide the temporary database entry to the database. The SQI is programmed to obtain a database entry and the temporary database entry from the database and generate an output based on the database entry and the temporary database entry.

Abstract: A network device includes a database that includes a number of tables, an observer, and a query service (QS) manager. The observer monitors an element of a first table of the number of tables and provide a value of the element to a query instance of a number of query instances. The QS manager generate the number of query instances. The query instance of the number of query instances executes a compiled query in response to receiving the value.

Abstract: A network device includes a query service instance (QSI), a database, and an observer. The QSI is programmed to generate an output based on a, at least in part, a first table of a database; send the output to the database for storage; and send a query completion indicator to the database. The database is programmed to store the output in a second table of the database. The observer is programmed to obtain the query completion indicator from the database and notify an entity that the QSI is complete in response to obtaining the query completion indicator.

Abstract: A network device includes a standing query instance (SQI) and a database. The SQI is programmed to generate an output stored in a low resource storage table of a database. The database is programmed to monitor a storage capacity of the low resource storage table based on at least, in part, the output stored in the low resource storage table; determine, based on the monitoring, when the storage capacity reaches a predetermined amount; and disable an upstream element in response to the determination.

Abstract: A network device includes a database that includes a materialized table and a non-materialized table. The network device also includes a standing query instance that generates an output that is stored in the non-materialized table. The database obtains a request that specifies the output, and provides the output in response to the request.

Abstract: A network device includes an external subscription table, an interpreter, and a state machine. The external subscription table includes a subscription associated with a client. The interpreter is programmed to obtain the subscription; generate an entity, based on the subscription, that produces an output; and notify the client of the output. The state machine is programmed to send the output to the client based on the subscription.

Abstract: A method for operating a network element includes obtaining a write request that specifies a variable length data. The method includes identifying a row of a table based on the write request. The method includes processing the row to identify an empty portion of a variable length data storage portion of the row. The method includes determining an offset that that specifies the location of the empty portion. The method includes storing the offset and a length of the variable length data in a fixed length storage element of the fixed length data storage portion. The method includes storing the variable length data in the empty portion of the variable length data storage portion.

Abstract: A network device includes a database that includes a number of tables, an observer, and a query service (QS) manager. The observer monitors an element of a first table of the number of tables and provide a value of the element to a query instance of a number of query instances. The QS manager generate the number of query instances. The query instance of the number of query instances executes a compiled query in response to receiving the value.

Abstract: A network device includes a standing query (SQ) service manager. The SQ service manager may obtain a standing query (SQ) request; determine a location of a table specified in the SQ request; identify a target location based on, at least in part, the location of the table; and generate a SQ instance based on the target location and SQ request. The target location is the network device.

Abstract: A network device includes an external subscription table, an interpreter, and a state machine. The external subscription table includes a subscription associated with a client. The interpreter is programmed to obtain the subscription; generate an entity, based on the subscription, that produces an output; and notify the client of the output. The state machine is programmed to send the output to the client based on the subscription.

Abstract: A network device includes a database that includes a materialized table and a non-materialized table. The network device also includes a standing query instance that generates an output that is stored in the non-materialized table. The database obtains a request that specifies the output, and provides the output in response to the request.

Abstract: A network device includes a connection manager and a state machine. The connection manager is programmed to establish a connection with a client; send, using the connection, a database planner to the client; obtain, using the connection, a subscription request from the client; and modify the database planner based on the subscription request. The state machine is programmed to process the database planner.

Abstract: A method for operating a network element includes obtaining a write request that specifies a variable length data. The method includes identifying a row of a table based on the write request. The method includes processing the row to identify an empty portion of a variable length data storage portion of the row. The method includes determining an offset that that specifies the location of the empty portion. The method includes storing the offset and a length of the variable length data in a fixed length storage element of the fixed length data storage portion. The method includes storing the variable length data in the empty portion of the variable length data storage portion.

Abstract: A network device includes a database that includes database entries, an external data that includes external data entries, an interpreter, and a standing query instance (SQI). The interpreter is programmed to convert an external data entry into a temporary database entry and provide the temporary database entry to the database. The SQI is programmed to obtain a database entry and the temporary database entry from the database and generate an output based on the database entry and the temporary database entry.

Abstract: A network device includes a standing query instance (SQI) and a database. The SQI is programmed to generate an output stored in a low resource storage table of a database. The database is programmed to monitor a storage capacity of the low resource storage table based on at least, in part, the output stored in the low resource storage table; determine, based on the monitoring, when the storage capacity reaches a predetermined amount; and disable an upstream element in response to the determination.

Abstract: A network device includes a query service instance (QSI), a database, and an observer. The QSI is programmed to generate an output based on a, at least in part, a first table of a database; send the output to the database for storage; and send a query completion indicator to the database. The database is programmed to store the output in a second table of the database. The observer is programmed to obtain the query completion indicator from the database and notify an entity that the QSI is complete in response to obtaining the query completion indicator.

Abstract: Methods and systems are described for applying the use of shards within a single memory address space. A database request is processed by providing the request from a client to a processor, the processor then distributing the request to multiple threads within a single process but executing in a shared memory address environment, wherein each thread performs the request on a distinct shard, and aggregating the results of the multiple threads being aggregated and returning a final result to the client. By parallelizing operations in this way, the request response time can be reduced and the total amount of communication overhead can be reduced.

Abstract: Methods and systems are described for applying the use of shards within a single memory address space. A database request is processed by providing the request from a client to a processor, the processor then distributing the request to multiple threads within a single process but executing in a shared memory address environment, wherein each thread performs the request on a distinct shard, and aggregating the results of the multiple threads being aggregated and returning a final result to the client. By parallelizing operations in this way, the request response time can be reduced and the total amount of communication overhead can be reduced.

Abstract: Software agents perform a process to monitor the availability and/or performance of various functions of a messaging system. A call is initiated to an endpoint, where the endpoint is registered with a messaging system and is configured to forward incoming messages to the messaging system. A first agent transmits a message to the endpoint for forwarding to the messaging system. A second agent determines whether the endpoint receives a message notification. In an embodiment, the time that elapses between arrival of the message at the endpoint and reception of a message notification is determined. In an embodiment, if the second agent is able to retrieve the transmitted message, then the retrieved message is compared with the version of the original message that was received at the endpoint. Whether the retrieved message suffered any degradation from its path through the messaging system is determined based on the comparison.

Abstract: Software agents perform a process to monitor the availability and/or performance of various functions of a messaging system, such as a Unified Messaging System. A call is initiated to an endpoint, where the endpoint is registered with a messaging system and is configured to forward incoming messages to the messaging system. A first agent transmits a message to the endpoint for forwarding to the messaging system. A second agent that is associated with the endpoint then determines whether the endpoint receives a message notification in response to the transmitted message. In an embodiment, the time that elapses between arrival of the message at the endpoint and reception of a message notification is determined. In an embodiment, if the second agent is able to access a mailbox and retrieve the transmitted message, then the message retrieved from the messaging system is compared with the version of the original message that was received at the endpoint.