Abstract: A test application programming interface (API) request may be issued to a test service implementation. A test API response, which is responsive to the test API request, may be received from the test service implementation. First contents of the test API response may be compared to second contents of a control API response. The comparing may be performed based at least in part on a set of one or more expected differences associated with the test API response and the control API response. It may be determined, based on the comparing, whether an unexpected difference exists between the test API response and the control API response. An indication may be provided of whether the unexpected difference exists between the test API response and the control API response, and the unexpected difference may be automatically corrected, such as via one or more configuration changes.

Abstract: Responsive to a configuration event, a controller instance generates, according to a current version of a configuration interface between the controller instance and a data instance, a configuration message. The configuration message is obtained, via message service, by remote data instances. The remote data instances attempt to process the configuration message, according to whichever version of the configuration interface the respective data instances are using. Appropriate acknowledgements (based on whether the remote data instances could fully process the configuration message or not) are generated and returned to the controller instance that marks a record for the configuration message as complete for the remote instance or marks the record for the configuration message to be re-sent for the remote instance. After waiting some period of time to allow data instances with out-of-date versions to update, a configuration message update cycle re-sends the message to the appropriate remote data instances.