Abstract: In an example embodiment, data communications to a first database intercepted and divided based on tenant. For each tenant of multiple tenants sharing the first database, the commands to update the one or more records in the first database within the data communications corresponding to the tenant are translated into commands to update one or more records in a second database of a different type than the first database, the translated commands corresponding to the tenant are replayed against a copied version of the first database in the second database, and the performance of the second database in handling the translated commands during the replaying is tracked. Serialization and timely execution, among the translated commands corresponding to the tenant, of execution of the translated commands is maintained during the replaying and synchronization of execution of translated commands between multiple tenants is maintained.

Abstract: In an example embodiment, data communications to a first database intercepted and divided based on tenant. For each tenant of multiple tenants sharing the first database, the commands to update the one or more records in the first database within the data communications corresponding to the tenant are translated into commands to update one or more records in a second database of a different type than the first database, the translated commands corresponding to the tenant are replayed against a copied version of the first database in the second database, and the performance of the second database in handling the translated commands during the replaying is tracked. Serialization and timely execution, among the translated commands corresponding to the tenant, of execution of the translated commands is maintained during the replaying and synchronization of execution of translated commands between multiple tenants is maintained.

Abstract: A mechanism for executing a remote command in a stateless client/server environment that provides progress information and allows user input that can influence command execution. A server receives a command request thread and processes the thread asynchronously by launching an asynchronous thread of execution and creating a conversation identifier for identifying the thread. In executing the command thread, if a conflict in execution of the thread exists, the server halts execution of the thread, creates a user input request to provide a resolution to the conflict and a user input request identifier, and sends the user input request, user input request identifier, and conversation identifier to the client. Responsive to receiving a response from the client, the server processes the user input and resumes execution of the command thread based on the user input.

Abstract: A mechanism for executing a remote command in a stateless client/server environment that provides progress information and allows user input that can influence command execution. A server receives a command request thread and processes the thread asynchronously by launching an asynchronous thread of execution and creating a conversation identifier for identifying the thread. In executing the command thread, if a conflict in execution of the thread exists, the server halts execution of the thread, creates a user input request to provide a resolution to the conflict and a user input request identifier, and sends the user input request, user input request identifier, and conversation identifier to the client. Responsive to receiving a response from the client, the server processes the user input and resumes execution of the command thread based on the user input.