Ebay, Incorporated

Amazon Technologies, Inc.

Paypal, Inc.

Bhaven Avalani

Zahid N Ahmed

Alon Cohen

Ray Hideki Tanaka

Daniel Tsun Kao

Gary Yue

Sastry K Malladi

Abhinav Kumar

Ronald Francis Murphy

Sharad R Murthy

Wei Fang

Xinglang Wang

Hongyue Nemo Chen

Tony Chung Tung Ng

Weiwei Jin

Mingming Wang

Ippokratis Pandis

Rami El-Charif

Weian Deng

Changyi Zhu

Martin Grund

Sergei Nikolaev

Anurag Windlass Gupta

Andrew Edward Caldwell

Naresh Chainani

Michail Petropoulos

John Benjamin Tobler

Andi Gutmans

Sami Ben-Romdhane

Ankit Kumar Jain

Frederick Ryan Johnson

Sami Ben Romdhane

Srividhya Srinivasan

Min Zhou

Naveen Muralimanohar

Ramakrishna Kotla

Yousuf Hussain Syed Mohammad

William Michael McCreedy

Ankit Malpani

James Thomas Kiraly

Arun Raj Mony

Ping Zhao

Arun Rai Mony

Partha V Kanuparthy

Joydeep Sinha

Kaituo Li

Michalis Petropoulos

Eli R Fisher

Systems and techniques are described herein for tiered storage of customer data accessed by a search service of a computing resource service provider. In some aspects, customer data may be received by a search instance executed across a plurality of compute nodes and provisioned by a search service. The customer data may be indexed and the data and resulting index may be stored locally by a first pool of hot compute nodes of the search instance. The customer data and index may be migrated and stored remotely by a data storage service. Metadata associated with the customer data and/or index may be stored in a second pool of warm compute nodes of the search instance. The warm compute nodes, upon receiving a request to access the customer data, may identify a location of the customer data and retrieve the customer data from the data storage service according to the metadata.

Warm tier storage for search service

Burst performance of a database query may be determined according to a size of the database query. A query to a database may be received. A size may be determined for the query. If the size is less than a size threshold assigned to a first query engine, then the query may be performed at the first query engine. If the size is greater than or equal to the size threshold assigned to the first query engine, then the query may be performed at a second query engine.

Burst performance of database queries according to query size

Disclosed are a system comprising a computer-readable storage medium storing at least one program, and a computer-implemented method for event messaging over a network. A subscription interface receives data indicative of a subscription request for sessionized data. An allocation module allocates a sessionizer bank linked to the subscription request. A messaging interface module provisions identifiers linked to the respective processing engines of the sessionizer bank. The messaging interface module registers the allocated sessionizer bank as available to process event messages matching the subscription request by providing the provisioned identifiers. The messaging interface module receives event messages from a producer device linked by a collection server to a selected one of the processing engines of the sessionizer bank. The selected one of the processing engine processes the received event messages in accordance with session rule data linked to the subscription request to generate sessionized data.

Processing high volume network data

Granular performance analysis may be performed for database queries. Database query performance may be monitored. For some database queries, performance of portions of the database query may be measure. The measure performance of the portions may be compared with performance goals that correspond to the portions of the database query. Portions that do not meet or exceed the corresponding performance goals may be identified so that an indication of the identified portions may be provided.

Granular performance analysis for database queries

In one example, a server system facilitates an exchange of messages with a remote client application. An Application Program Interface (API) receives a first request message and a second request message, wherein the first request message includes a first data payload defined by a common definition and including a first payload data, the first payload defined by a first schema definition. The second request message includes a second data payload defined by the common definition and a second payload data, wherein the second payload is defined by a second schema definition different than the first schema definition. In response to receiving the first request message, the API transmits a first response message, and in response to receiving the second request message, the API transmits a second response.

API and business language schema design framework for message exchanges

Caching results of sub-queries to different locations in a data store may be performed. A database query may be received that causes different storage engines to perform sub-queries to different locations in a data store that stores data for a database. The results of the sub-queries may be stored in a cache. When another database query is received, sub-queries generated to perform the other database query that are the same as one or more of the previously performed sub-queries may obtain the results of the sub-queries from the cache instead of performing the sub-queries again.

Caching results for sub-queries to different data store locations

In various embodiments, a system, method, and a computer-readable medium for performing operations for tracking numerous software calls in an enterprise environment is provided. The method includes tracking, during a runtime operation of an enterprise environment, layers through which software calls pass. The tracking includes logging physical components involved in each of the software calls, annotating each of the physical components with metadata that is directly indicative of each of the physical components, and logging a reliance of each of the physical components on others of the physical components. Other systems and methods are disclosed.

Flow tracing of software calls

In one example, a server system in an electronic trading system facilitates an exchange of messages with a remote client application. An Application Program Interface (API) receives a first request message and a second request message, wherein the first request message including a first data payload defined by a common data component and including a first extended payload data, the first extended payload defined by a first schema definition. The second request message includes a second data payload defined by the common data component and a second extended payload data, wherein the second extended payload is defined by a second schema definition different than the first schema definition. In response to receiving the first request message, the API transmits a first response message, and in response to receiving the second request message, the API transmits a second response message different than the first response message.

A computer-implemented system and method for decoupling processing of request and response messages supporting different pluggable respective transports in a service-oriented pipeline architecture for a request-response Message Exchange Pattern (MEP) is disclosed. The method in an example embodiment includes receiving a message having coded therein information identifying a desired pluggable transport mechanism respectively for a request and a response; processing the message through a message processing pipeline; dispatching the processed message to a dispatcher; determining if the desired pluggable transport mechanism is available; activating the desired pluggable transport mechanism, if the desired pluggable transport mechanism is available; and transporting the processed message via the desired pluggable transport mechanism.

Request and response decoupling via pluggable transports in a service oriented pipeline architecture for a request response message exchange pattern

A method of accommodating at least one difference between a first database schema and a second database schema is provided. The method includes receiving a request generated by an application program using a first version of a database schema, and generating a response including a reserved element that corresponds to a custom slot provided in the first version of the database schema. The method further includes communicating the response to the application program.

Techniques for maintaining compatibility in database schemas

Systems, methods and media are provided for facilitating an exchange of messages between a remote client application and a server system the server system, the server system being capable of supporting a plurality of application program interfaces (APIs) that includes a targeted API. In one example, a method includes receiving a plurality of request messages generated by the remote client application, each request message requesting an activity to be performed by the targeted API, with respect to an associated application, and comprising at least one data component common to each of the plurality of request messages and selected from a group comprising a predetermined required level of detail, an error language component and a version identifier, and a request component including a reusable identified schema definition.

Growing community of inventors

Cupertino, CA, United States of America

Bhaven Avalani