Abstract: Architectures and techniques are described related to identifying merchants associated with information obtained from a number of sources and storing portions of the information in data elements related to the merchants. The information may be provided in a structured format that enables the service provider to associate certain information with a particular merchant or in an unstructured format. The service provider may analyze the information received from the sources to determine whether the information includes any merchant identifying information. When the service provider identifies a merchant based on the merchant identifying information, the service provider may extract additional portions of the information received (e.g. merchant reviews, merchant attributes, etc.) and store those additional portions of information in the data element of the merchant.

Abstract: The techniques described herein provide software testing of a candidate version of software. In some examples, an interceptor intercepts at least one production request to a production version of the software and issues the production request to a shadow proxy service as a shadow request. The shadow proxy service causes the at least one shadow request to be processed by the candidate version of the software being validated and an authority version of the software being used to validate the candidate version. The shadow proxy service may then compare and/or analyze at least one candidate response to the shadow request from the candidate version and at least one authority response to the shadow request from the authority version. A dashboard service may provide at least some of the resulting information and issue a request the shadow proxy service to replay at least one of the shadow requests.

Abstract: The techniques described herein provide software testing of a candidate version of software. In some examples, an interceptor intercepts at least one production request to a production version of the software and issues the production request to a shadow proxy service as a shadow request. The shadow proxy service causes the at least one shadow request to be processed by the candidate version of the software being validated and an authority version of the software being used to validate the candidate version. The shadow proxy service may then compare and/or analyze at least one candidate response to the shadow request from the candidate version and at least one authority response to the shadow request from the authority version. A dashboard service may provide at least some of the resulting information and issue a request the shadow proxy service to replay at least one of the shadow requests.