Amazon Technologies, Inc.

William Wallace Allocca

Ram Cherukuri

James Cade Bodley

Nandan Ulhas Telang

Jeffrey P Bezos

Maryam S Mohit

Suguna Subramaniam

James Prudente

Jordan Maureen Hay

Colleen McQueen

Walker L Lockhart

Ericka N Lock

Jonathan A LeBlang

Nitin Sivakrishnan

Harsha Ramalingam

Bharathi Masilamani

Hemanth Kumar Reddy Vallela

Michael Carl Brant

Vemaganti Amith Vikram

Vikas Singh

Sanyuan Tang

Ohm Reddy Bomedi

Arun Vashishtha

Soumya Ranjan Maharana

Hareendra Sura

Anil Kumar Senesetti

Techniques describing methods and systems for validating different versions of a set of rules for performing automated workflow processes. Sets of input data, each disjoint from one another, are obtained that are optimized from inputs contained in data storage. A first output is produced using one or more of the sets of inputs as input to a first version of the set of rules, and a second output is produced using the one or more of the sets of inputs as input to a second version of the set of rules. The first output is compared with the second output and, in response to a determination that the first output and the second output do not match, an indication of inconsistency is recorded.

Automated workflow validation using rule-based output mapping

The systems and techniques described herein optimize processing of requests, such as external requests, internal requests or inter-service requests. In some examples, a service may interact with a client device and determine, based at least in part on a state of the interaction with the client device, a potential client request that may subsequently be received from the client device. The service may then perform one or more actions to at least partially fulfill the potential client request.

Optimization of production systems

The techniques described herein provide software testing of a candidate version of software. In some examples, an interceptor may perform an asynchronous and non-blocking intercept of at least one request to a production system and may provide the intercepted at least one request to a shadow proxy service as at least one shadow request. The shadow proxy service may process the shadow request by causing the at least one shadow request to be classified based at least one criteria. The processed shadow requests are logged. A selection may be made from among the logged shadow request to be replayed by the production system based on one or more criteria used to classify the shadow requests. The shadow proxy service may replay the selected at least one logged shadow request to the production system.

A method and system for placing an order to purchase an item via the Internet. The order is placed by a user at a client system and received by a server system. The client system can display information identifying the item and, for each of multiple procurement options having information related to ordering the identified item, can display an indication of the procurement option such that selection of the displayed indication represents an ordering of the identified item using the information of the procurement option. In response to selection of a displayed indication, the client system can send to a server computer a request to order the identified item using the information of the procurement option for the selected indication.

Placing a purchase order using one of multiple procurement options

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.

Shadow test replay service

The techniques described herein provide for comparison of tree structures. In some examples, a system according to this disclosure may receive at least a first item including a first tree structure and a second item including a second tree structure. The system may compare the first item and the second item. In particular, in performing the comparison, the system may detect a sub-tree structure type in the first tree structure and in the second tree structure. In some examples, the sub-tree structure type is one of one or more sub-tree structure types that have corresponding matching processes. Once determined, the system described herein may perform the corresponding matching process of the detected sub-tree structure type for the first tree structure and the second tree structure.

Tree comparison functionality for services

An interactive system personalizes pages of an electronic catalog with information reflective of related orders placed by the user. In one embodiment, when a user requests a category page (such as a browse node page, author page, or artist page) of an electronic catalog, the system determines whether the user previously ordered any items falling within the associated category. If any such orders are identified, information regarding the prior order(s) is incorporated into the requested category page. This information may include, for example, an indication of the particular item(s) ordered, and the order date and/or status of each such order. The system may also personalize item detail pages with information regarding any orders placed for the corresponding items and/or similar items.

Contextual presentation on electronic catalog pages of information reflective of prior orders

An electronic catalog system, which may be implemented as a web site or another type of interactive system, presents context-sensitive information to customers reflective of their prior orders. In one embodiment, when a customer requests an item detail page for a particular item, the system may supplement the item detail page with information reflective of one or more related orders previously placed by the customer. This information may include, for example, an indication that the customer previously ordered this item or a related item, and may include information, such as status information, regarding such previously placed order(s). If the customer previously ordered a related item, the information provided on the item detail page may include an indication of whether the previously ordered item is compatible or interoperable with the item being viewed.

An electronic catalog system, which may be implemented as a web site or another type of interactive system, presents context-sensitive account information to customers during browsing of an electronic catalog of products. In one embodiment, when a customer accesses a detail page for a particular product, the detail page is supplemented with information, such as status information, about a related order placed by the customer. The related order may be an order for the product represented in the detail page or may be for a related product. Information about related orders may additionally or alternatively be added to other types of pages, such as product category pages and shopping cart pages. In one embodiment, a customer's related order information is maintained in a cache during the customer's browsing session, and the cache is updated in real time to reflect actions performed by the customer.

Contextual presentation of information about related orders during browsing of an electronic catalog

An online store system, which may be implemented as a web site or another type of interactive system, presents context-sensitive information to customers about their prior orders during browsing of an electronic catalog of products. In one embodiment, when a customer accesses a detail page for a particular product, the detail page is supplemented with information, such as status information, about a related order placed by the customer. The related order may be an order for the product represented in the detail page or may be for a related product. Information about related orders may additionally or alternatively be added to other types of pages, such as product category pages and shopping cart pages. In one embodiment, a customer's related order information is maintained in a cache during the customer's browsing session, and the cache is updated in real time to reflect actions performed by the customer.

Growing community of inventors

Bellevue, WA, United States of America

William Wallace Allocca