Abstract: Embodiments presented herein provide techniques for evaluating an asynchronous application using a test framework. The test framework may perform a load test of an asynchronous application or service composed from a collection of applications or services. To do so, the test framework may submit transactions to a distributed application at a specified transaction rate and monitor how the distributed application operates at that transaction rate. An aggregate load test component may evaluate the remaining work pending at work accumulation points of the distributed application to determine whether the distributed application can sustain the specified transaction rate. A transaction tracking component may initiate transactions to generate load at the specified transaction rate without blocking while the transactions are processed by the distributed application.

Abstract: Methods, systems, and computer-readable media for record-by-record live migration using segmentation are disclosed. Migration of a data set comprises, for a record in a segment being migrated, storing a first status indicating that the record is offline in a source data store. An instance of the record is stored in the destination data store, and a second status is stored to indicate that the record is online in the destination. The record is deleted from the source after the second status is stored. During the migration, a read request for the record is received and determined to be associated with the segment being migrated. A response to the read request is generated that comprises an authoritative instance of the record. The instance of the record in the destination is determined to represent the authoritative instance based (at least in part) on the first status and the second status.

Abstract: Methods, systems, and computer-readable media for segmentation of maintenance on distributed systems are disclosed. A data set is partitioned according to a hash function into a plurality of segments. A maintenance activity is initiated on a first segment. During the maintenance activity, a first request to perform a first action on the data set is received. Based at least in part on determining that the first request is associated with the first segment using the hash function, the first action is performed using additional processing associated with the maintenance activity. During the maintenance activity, a second request to perform a second action on the data set is received. Based at least in part on determining that the second request is associated with a second segment using the hash function, the second action is performed without the additional processing associated with the maintenance activity.

Abstract: Items within a data set can be redistributed to different partitions of a distributed data store according to modified hash values. A redistribution event may, in some embodiments, trigger the redistribution of a data set. Modified hash values for items in the data set may be generated according to a secondary hashing scheme to be used for identifying the location of a new partition to store the item instead of hash values based on current key values that identify a current partition that stores the item. Access can be provided to items based on the modified hash values to determine the new partition that stores the item after redistribution.

Abstract: Embodiments presented herein provide techniques for evaluating an asynchronous application using a test framework. The test framework may perform a load test of an asynchronous application or service composed from a collection of applications or services. To do so, the test framework may submit transactions to a distributed application at a specified transaction rate and monitor how the distributed application operates at that transaction rate. An aggregate load test component may evaluate the remaining work pending at work accumulation points of the distributed application to determine whether the distributed application can sustain the specified transaction rate. A transaction tracking component may initiate transactions to generate load at the specified transaction rate without blocking while the transactions are processed by the distributed application.

Abstract: Sequence diagrams and executable stub modules are generated based on log data associated with a transaction. A sequence diagram generator receives data identifying a relationship between one or more requests and one or more replies stored in the log data. The sequence diagram describes the flow of events of any transaction described by the log data. A stub module comprising executable code in one or more programming languages may be automatically generated using the sequence diagram as input. The stub module may be executed to implement similar functionality of one or more components of the transaction described in the log data.