Abstract: Certain example embodiments involve accessing data in a database. At least one key is associated with the data. The data is indexed based on the at least one key. The index provides key-value pairs in which keys in the key-value pairs correspond to the at least one key associated with the data and values in the key-value pairs correspond to deserializable serialized blobs generated to include the data in variant data type format. The variant data type format includes different possible equivalent representations of the data such that the data stored in the blobs is of potentially different structures. Responsive to a request received from a computing device, a database transaction is performed on the data in connection with the index and based on the received request. These techniques can be used in connection with tasks as well as data “per se.” O(1) performance is achievable in some instances.

Abstract: Certain example embodiments involve accessing data in a database. At least one key is associated with the data. The data is indexed based on the at least one key. The index provides key-value pairs in which keys in the key-value pairs correspond to the at least one key associated with the data and values in the key-value pairs correspond to deserializable serialized blobs generated to include the data in variant data type format. The variant data type format includes different possible equivalent representations of the data such that the data stored in the blobs is of potentially different structures. Responsive to a request received from a computing device, a database transaction is performed on the data in connection with the index and based on the received request. These techniques can be used in connection with tasks as well as data “per se.” O(1) performance is achievable in some instances.

Abstract: Certain example embodiments relate to an inline dispatching function interface (IDFI) statically linked to an application and dynamically linkable to at least one library. The IDFI is transparent to the application. Processing resources maintain a process space and execute the application in connection with it. The at least one library is usable by, but external to, the application. The IDFI is configured to at least: automatically reload the at least one library into the process space during runtime in response to a detected trigger event, without interrupting processing of the application, and while also automatically synchronizing processing threads relevant to execution of the at least one library; receive, from the application and through header file directives added to the application during compilation of the application, a call for a function of the at least one library; and responsive to reception of the call, execute the call to the function.

Abstract: Certain example embodiments relate to an inline dispatching function interface (IDFI) statically linked to an application and dynamically linkable to at least one library. The IDFI is transparent to the application. Processing resources maintain a process space and execute the application in connection with it. The at least one library is usable by, but external to, the application. The IDFI is configured to at least: automatically reload the at least one library into the process space during runtime in response to a detected trigger event, without interrupting processing of the application, and while also automatically synchronizing processing threads relevant to execution of the at least one library; receive, from the application and through header file directives added to the application during compilation of the application, a call for a function of the at least one library; and responsive to reception of the call, execute the call to the function.