Abstract: Systems and methods include receiving an exception raised by a database storage system in response to a database operation requested by an application, providing, in response to the exception, the application with a pointer to a failover framework comprising a memory store, receiving, from the application and at the failover framework, a request to write first data, storing, in response to the request to write first data, the first data in a tree structure of the memory store in chronological order, receiving, from the application and at the failover framework, a request to read second data, and, in response to the request to read second data, sorting the tree structure primarily by user and secondarily by chronological order and reading the second data from the sorted tree structure.

Abstract: Systems and methods include receiving an exception raised by a database storage system in response to a database operation requested by an application, providing, in response to the exception, the application with a pointer to a failover framework comprising a memory store, receiving, from the application and at the failover framework, a request to write first data, storing, in response to the request to write first data, the first data in a tree structure of the memory store in chronological order, receiving, from the application and at the failover framework, a request to read second data, and, in response to the request to read second data, sorting the tree structure primarily by user and secondarily by chronological order and reading the second data from the sorted tree structure.

Abstract: A service request is received. A universal service request ticket is created for the service request. The service request is routed to a dynamically selected service domain including by creating for the dynamically selected service domain a child service request ticket of the universal service request ticket. A status of the universal service request ticket is updated based on a status of the child service request ticket of the dynamically selected service domain.

Abstract: Example embodiments for controlling access in a network system based on a distributed ledger are presented. In an example embodiment, a plurality of nodes of a computer network capture information describing requested data transactions in the computer network. At least some of the nodes construct transaction blocks for a distributed ledger, with each of the transaction blocks including information describing one or more of the requested data transactions. The nodes publish the transaction blocks to other nodes. The nodes receiving the transaction blocks add those of the transaction blocks that do not include a disallowable requested data transaction to copies of the distributed ledger. One or more arbitrator nodes approve those of the requested data transactions represented in transaction blocks added to the copies of the distributed ledger by a consensus of the nodes.

Abstract: Systems and methods are provided for receiving data and uploading it into an in-memory database using a set of predefined procedures. The data includes a plurality of data records. A plug-in embedded in the in-memory database detects the uploaded data and a structure corresponding to the uploaded data. A user interface (UI) template is created on the detected structure of the uploaded data. From the UI template, a web application is created. By activating the web application, an end-user UI is created which includes a plurality of graphical user interface elements corresponding to the uploaded data. The end-user UI is initiated for rendering in a graphical user interface.

Abstract: Example embodiments for controlling access in a network system based on a distributed ledger are presented. In an example embodiment, a plurality of nodes of a computer network capture information describing requested data transactions in the computer network. At least some of the nodes construct transaction blocks for a distributed ledger, with each of the transaction blocks including information describing one or more of the requested data transactions. The nodes publish the transaction blocks to other nodes. The nodes receiving the transaction blocks add those of the transaction blocks that do not include a disallowable requested data transaction to copies of the distributed ledger. One or more arbitrator nodes approve those of the requested data transactions represented in transaction blocks added to the copies of the distributed ledger by a consensus of the nodes.

Abstract: Systems and methods are provided for receiving data and uploading it into an in-memory database using a set of predefined procedures. The data includes a plurality of data records. A plug-in embedded in the in-memory database detects the uploaded data and a structure corresponding to the uploaded data. A user interface (UI) template is created on the detected structure of the uploaded data. From the UI template, a web application is created. By activating the web application, an end-user UI is created which includes a plurality of graphical user interface elements corresponding to the uploaded data. The end-user UI is initiated for rendering in a graphical user interface.