Abstract: Multiple versions of a service can be supported by taking advantage of the fact that version information can be included in any received request. Multiple templates may be stored, with each template being associated with a particular version of the service. There may also be multiple templates associated with each version of a service for various response types. Using the version information, an appropriate template can be determined up front to be used for the response. An instance of the template can be filled in using appropriate data sources, as may be specified using metadata in the template itself. Once the instance of the template is filled, the response can be finalized and sent.

Abstract: Multiple structured documents can be compared with one another utilizing user-specified custom configurations. For example, a traversal of at least two of the documents may identify one or more potential matches in the documents. A user-defined rule may be obtained that specifies differences that are expected within the documents. Additionally, a determination may be made regarding when differences between potential matches are significant based in part on user-defined rule. In some examples, significant differences may be determined to be significant as a result of being differences, other than expected differences, that vary from the expected differences. Any significant differences can be logged, reported on or added to statistics for the new service being tested.

Abstract: Multiple versions of a service can be supported by taking advantage of the fact that version information can be included in any received request. Using the version information, an appropriate template can be determined up front to be used for the response. In instance of the template can be filled in using appropriate data sources, as may be specified using metadata in the template itself. Information can be processed in parallel, respecting any data dependencies specified by the template metadata. Once the instance of the template is filled, the response can be finalized and sent to the source of the request.

Abstract: A new service, or new version of an existing service, can be tested using actual production requests and services. A request received by a production service, along with the response generated by the production service, is forwarded to a shadow service. The shadow service forwards the request to the new service, which generates a test response and sends the test response back to the shadow service. The shadow service utilizes a comparison engine operable to compare the responses for significant differences. Any significant differences can be logged, reported on, or added to statistics for the new service being tested.

Abstract: A new service, or new version of an existing service, can be tested using actual production requests and services. A request received by a production service, along with the response generated by the production service, is forwarded to a shadow service. The shadow service forwards the request to the new service, which generates a test response and sends the test response back to the shadow service. The shadow service utilizes a comparison engine operable to compare the responses for significant differences. Any significant differences can be logged, reported on, or added to statistics for the new service being tested.