Abstract: Techniques are disclosed relating to transitioning between data stores using a data migration server. In some embodiments, the data migration server may be used to access data stored on a preexisting data store to service requests from a plurality of services. A dual-write operation mode for the data migration server may then be enabled such that, in response to a given write request, the data migration server writes a given data entry to both the preexisting data store and a replacement data store. Further, a dual-read operation mode may be enabled such that, in response to a given read request, the data migration server reads a corresponding data entry from both the preexisting and replacement data stores. Configuration settings for the data migration server may then be adjusted to designate the replacement data store as the primary data store to service requests from the services.

Abstract: Techniques are disclosed relating to transitioning between data stores using a data migration server. In some embodiments, the data migration server may be used to access data stored on a preexisting data store to service requests from a plurality of services. A dual-write operation mode for the data migration server may then be enabled such that, in response to a given write request, the data migration server writes a given data entry to both the preexisting data store and a replacement data store. Further, a dual-read operation mode may be enabled such that, in response to a given read request, the data migration server reads a corresponding data entry from both the preexisting and replacement data stores. Configuration settings for the data migration server may then be adjusted to designate the replacement data store as the primary data store to service requests from the services.

Abstract: Techniques are disclosed relating to transitioning between data stores using a data migration server. In some embodiments, the data migration server may be used to access data stored on a preexisting data store to service requests from a plurality of services. A dual-write operation mode for the data migration server may then be enabled such that, in response to a given write request, the data migration server writes a given data entry to both the preexisting data store and a replacement data store. Further, a dual-read operation mode may be enabled such that, in response to a given read request, the data migration server reads a corresponding data entry from both the preexisting and replacement data stores. Configuration settings for the data migration server may then be adjusted to designate the replacement data store as the primary data store to service requests from the services.

Abstract: Techniques are disclosed relating to transitioning between data stores using a data migration server. In some embodiments, the data migration server may be used to access data stored on a preexisting data store to service requests from a plurality of services. A dual-write operation mode for the data migration server may then be enabled such that, in response to a given write request, the data migration server writes a given data entry to both the preexisting data store and a replacement data store. Further, a dual-read operation mode may be enabled such that, in response to a given read request, the data migration server reads a corresponding data entry from both the preexisting and replacement data stores. Configuration settings for the data migration server may then be adjusted to designate the replacement data store as the primary data store to service requests from the services.

Abstract: Methods and systems for providing an external scheduler in a stateless application framework are presented. A first instance of a stateless application transmits a job request to a data processing engine, and submits a message to a messaging queue. The message indicates a task to be performed according to a delayed schedule. The first instance of the stateless application terminates after submitting the message. The messaging queue transmits the message to the stateless application framework according to the delayed schedule. Upon receiving the message, a second instance of the stateless application is instantiated. The second instance of the stateless application performs an action based on the message and terminates.

Abstract: Methods and systems for providing a stateless application framework are presented. The stateless application framework is utilized by different applications for implementing different workflows. Each workflow may be associated with one or more state machine configurations representing the different states within the workflow. Upon receiving an indication of an event from an application, a stateless application module transmits a job request to a data processing engine based on a current state of the event. When a response is received from the data processing engine, the state application module determines whether the state of the event has been updated since transmitting the job request. If it is determined that the state has been updated, the stateless application module is configured to transmit another job request to the data processing engine based on the updated state of the event.

Abstract: Methods and systems for providing an external scheduler in a stateless application framework are presented. A first instance of a stateless application transmits a job request to a data processing engine, and submits a message to a messaging queue. The message indicates a task to be performed according to a delayed schedule. The first instance of the stateless application terminates after submitting the message. The messaging queue transmits the message to the stateless application framework according to the delayed schedule. Upon receiving the message, a second instance of the stateless application is instantiated. The second instance of the stateless application performs an action based on the message and terminates.

Abstract: Methods and systems for providing a stateless application framework are presented. The stateless application framework is utilized by different applications for implementing different workflows. Each workflow may be associated with one or more state machine configurations representing the different states within the workflow. Upon receiving an indication of an event from an application, a stateless application module transmits a job request to a data processing engine based on a current state of the event. When a response is received from the data processing engine, the state application module determines whether the state of the event has been updated since transmitting the job request. If it is determined that the state has been updated, the stateless application module is configured to transmit another job request to the data processing engine based on the updated state of the event.