Impinj, Inc.

Microsoft Technology Licensing, LLC

Amazon Technologies, Inc.

Sandesh Doddameti

Scott A Cooper

Kurt Eugene Sundstrom

Balaji Shyamkumar

Jayasuryan Iyer

Christopher J Diorio

Maneesh Sah

Jegan Devaraju

Rishabh Animesh

Himanshu Gupta

Shane Kumar Mainali

Ameet Nirmal Vaswani

Venkates Paramasivam Balakrishnan

Mark Christopher Seigle

Christopher Thomas

Ryan Charles Schmitt

Preetha Chatterjee

Paul Lee Coleman, Iv

Nan Zhong

Vikas Mehta

James Lee Baker

Erik Ackermann

Hao Wang

Vamshi Konagari

Ramy Wassef

Described herein is a system and method for an append-only block-oriented object storage system. An unstructured storage object is stored in cloud storage. A block is data is received, from a client, to append to the unstructured storage object. A universally unique identifier of the client, and client contextual information regarding the block of data, are received from the client. The client contextual information comprises an identifier of a most recently appended block from the client. When the identifier of the most recently appended block from the client matches a stored identifier associated with the universally unique identifier of the client, the block of data is appended to the unstructured storage object, and the stored identifier associated with the universally unique identifier of the client is updated in accordance with the received client contextual information.

Object storage change-events

Example aspects include techniques for ordering operations in a file system having a hierarchical namespace including determining, by a first service that manages file system operations for a first entity in the hierarchical namespace, to perform a file system operation for the first entity, generating, by the first service, a first counter record for the file system operation, obtaining, based on determining to perform the file system operation and from a second service that manages file system operations on a second entity that is a parent of the entity in the hierarchical namespace, a second counter record for a last file system operation performed on the second entity, wherein the second counter record is generated by the second service, and storing, in a change feed, an indication of the file system operation along with the first counter record and the second counter record.

Methods and systems for ordering operations on a file system having a hierarchical namespace

An RFID-based item tracking system may use statistical methods to determine whether a tag or tagged item that does not respond when inventoried is present in a particular zone or reader antenna field-of-view. In one embodiment, the item tracking system may determine an observability of an item based on one or more initial trials. Upon not detecting the item in one or more subsequent trials, the item tracking system may estimate whether the item is still present based on the observability.

RFID-based item presence detection

Described herein is a system and method for a user accessible log of object storage change-events system. A change is detected within a cloud storage based on an unstructured storage object stored in the cloud storage. Contextual attributes of the change are identified from an updated state of the log file that stores information about the unstructured storage object. An output is provided based, at least in part, upon the detected change and at least some of the contextual attributes, wherein the output is an immutable, read-only log of change events.

A computer system, such as a data storage system, implements techniques for managing unpredictable and/or bursty system demand. For example, a database service implements a schema and/or a database table rotation that allows for events to be allocated substantially evenly across the available keyspace. In some embodiments, asynchronous and synchronous components of a data processing system are accordingly isolated so as to improve the operational efficiency and utilization of both.

Techniques and systems for scalable request handling in data processing systems

Techniques described and suggested herein include implementations of caches and scalers to handle data storage requests, and storage event status requests associated with data storage requests, in a scalable fashion. For example, a data storage system, such as a data storage system implemented by a computing resource service provider in connection with providing an archival storage service or other data storage service, may be implemented to maintain a consistent response time and backend capability for incoming data storage requests, which may be a component of ensuring a consistent customer experience for customers of an associated service, with little or no regard to peaky or high data storage request rates observed by the implementing data storage system.

Techniques for adapting data storage systems for peaky usage models

Systems and methods provide automated provisioning of load balancing. In one implementation, a computer-implemented method configures an access point. A request to create the access point may be received and data for the access point may be stored in a data store. The method may invoke a workflow engine. The workflow engine may assign the access point to a load balancer, configure the load balancer, assign a network address to the load balancer, and publish the network address for a plurality of clients.

Automated load balancing architecture

Growing community of inventors

Seattle, WA, United States of America

Sandesh Doddameti