Abstract: A fleet of query accelerator nodes is established for a data store. Each accelerator node caches data items of the data store locally. In response to determining that an eviction criterion has been met, one accelerator node removes a particular data item from its local cache without notifying any other accelerator node. After the particular data item has been removed, a second accelerator node receives a read query for the particular data item and provides a response using a locally-cached replica of the data item.

Abstract: The present disclosure provides reduced cell-specific reference signal (CRS) transmissions for evolved machine type communication (eMTC). In one aspect, a network entity may determine at least one narrow band for transmission of a CRS. The network entity may further identify one or more resource blocks proximate the at least one narrow band and transmit the CRS on the narrow band and the one or more proximate resource blocks to a UE. In another aspect, a UE may apply a receive window to filter one or more noise samples outside at least one narrow band allocation, the receive window corresponding to one or more resource blocks located outside the defined number of resource blocks of the at least one narrow band allocation. The UE may further receive the CRS within the at least one narrow band allocation from a network entity in response to applying the receive window.

Abstract: The present disclosure provides reduced cell-specific reference signal (CRS) transmissions for evolved machine type communication (eMTC). In one aspect, a network entity may determine at least one narrow band for transmission of a CRS. The network entity may further identify one or more resource blocks proximate the at least one narrow band and transmit the CRS on the narrow band and the one or more proximate resource blocks to a UE. In another aspect, a UE may apply a receive window to filter one or more noise samples outside at least one narrow band allocation, the receive window corresponding to one or more resource blocks located outside the defined number of resource blocks of the at least one narrow band allocation. The UE may further receive the CRS within the at least one narrow band allocation from a network entity in response to applying the receive window.

Abstract: A fleet of query accelerator nodes is established for a data store. Each accelerator node caches data items of the data store locally. In response to determining that an eviction criterion has been met, one accelerator node removes a particular data item from its local cache without notifying any other accelerator node. After the particular data item has been removed, a second accelerator node receives a read query for the particular data item and provides a response using a locally-cached replica of the data item.

Abstract: Based at least in part on an optimization goal determined for a storage group comprising a plurality of data stores for which writes requests are coordinated by a log-based transaction manager, one or more lifecycle transitions are identified for data objects stored in a first data store. In accordance with a first lifecycle transition, a data object is to be transferred from the first data store to a second data store based at least in part on a duration for which the data object has been resident at the first data store. A transition agent is assigned by a configuration manager to implement the first lifecycle transition.

Abstract: A fleet of query accelerator nodes is established for a data store. A particular node stores a binary encoding of a data item in a local data cache. The encoding identifies a metadata record indicating names of attributes of the data item. In response to receiving a particular query directed to the data item, an executable code component generated to produce a result for the query is cached in a local query code cache. When a second query which meets a matching criterion is received, the executable code component is re-used to obtain a result for the second query.

Abstract: A remote distributed data store may be configured to process data updates received through invocation of a common API with reference to a common schema. A local data store may also be configured to process updates through the common API with reference to the common schema. Updates to the local data store may be mapped from the local data store schema to the common schema, and applied to the distributed data store. Updates to the distributed data store may be mapped from the common schema to the local data store schema. User identity may be verified to limit data synchronization to authorized users.

Abstract: An accelerator intermediary node (AIN) associated with a data store obtains an indication of a control setting to be applied with respect to a write request directed to a data item, where the control setting specifies a target for one or more of replication count, data durability, a transaction grouping with respect to a write request, or back-end synchronization node. Using the control setting, a write propagation node set is identified for the write request. The write propagation node set includes another accelerator intermediary node and/or a storage node of a data store. Respective operation requests corresponding to the write request are transmitted to one or more members of the write propagation node set. A write coordinator role may be verified prior to attempting a commit together of a plurality of write requests as part of a multi-write transaction.

Abstract: A remote distributed data store may be configured to process data updates received through invocation of a common API with reference to a common schema. A local data store may also be configured to process updates through the common API with reference to the common schema. Updates to the local data store may be mapped from the local data store schema to the common schema, and applied to the distributed data store. Updates to the distributed data store may be mapped from the common schema to the local data store schema. User identity may be verified to limit data synchronization to authorized users.

Abstract: The present disclosure provides reduced cell-specific reference signal (CRS) transmissions for evolved machine type communication (eMTC). In one aspect, a network entity may determine at least one narrow band for transmission of a CRS. The network entity may further identify one or more resource blocks proximate the at least one narrow band and transmit the CRS on the narrow band and the one or more proximate resource blocks to a UE. In another aspect, a UE may apply a receive window to filter one or more noise samples outside at least one narrow band allocation, the receive window corresponding to one or more resource blocks located outside the defined number of resource blocks of the at least one narrow band allocation. The UE may further receive the CRS within the at least one narrow band allocation from a network entity in response to applying the receive window.

Abstract: A fleet of query accelerator nodes is established for a data store. A particular node determines a write throughput limit for back-end writes from the fleet to the data store. A pool of write-back threads is established at the node. When a write request is received at the node, an entry is added to a selected partition of a write-back journal, and a write completion response is provided to the requester without applying the write to the data store. A write-back thread from the pool eventually schedules the back-end write.

Abstract: A configuration manager of a storage service receives a set of service requirements, comprising one or more of: a performance requirement for one or more types of storage operations, or an access interface type requirement Based on the service requirements, a candidate storage configuration that includes one or more data store instances and a first log-based transaction manager is generated. Subsequent to an approval of the first storage configuration by a client, the establishment of the data store instances and the log-based transaction manager is initiated.

Abstract: A configuration manager of a storage service receives a set of service requirements, comprising one or more of: a performance requirement for one or more types of storage operations, or an access interface type requirement Based on the service requirements, a candidate storage configuration that includes one or more data store instances and a first log-based transaction manager is generated. Subsequent to an approval of the first storage configuration by a client, the establishment of the data store instances and the log-based transaction manager is initiated.

Abstract: Data stores that are to be configured as members of a storage group on behalf of a client are identified. The client indicates one or more types of cross-data-store operations to be performed. A transaction manager that makes acceptance decisions for write requests directed to the members based at least partly on contents of a log is instantiated, and respective write transformers are set up for at least some of the types of cross-data-store operations. During a particular time period, the workload at the storage group is monitored, and the number and types of cross-data-store operations is determined. The results of the monitoring are used to determine a billing amount for the client based on a selected pricing policy.

Abstract: A remote distributed data store may be configured to process data updates received through invocation of a common API with reference to a common schema. A local data store may also be configured to process updates through the common API with reference to the common schema. Updates to the local data store may be mapped from the local data store schema to the common schema, and applied to the distributed data store. Updates to the distributed data store may be mapped from the common schema to the local data store schema. User identity may be verified to limit data synchronization to authorized users.

Abstract: A remote distributed data store may be configured to process data updates received through invocation of a common API with reference to a common schema. A local data store may also be configured to process updates through the common API with reference to the common schema. Updates to the local data store may be mapped from the local data store schema to the common schema, and applied to the distributed data store. Updates to the distributed data store may be mapped from the common schema to the local data store schema. User identity may be verified to limit data synchronization to authorized users.

Abstract: Data stores that are to be configured as members of a storage group on behalf of a client are identified. The client indicates one or more types of cross-data-store operations to be performed. A transaction manager that makes acceptance decisions for write requests directed to the members based at least partly on contents of a log is instantiated, and respective write transformers are set up for at least some of the types of cross-data-store operations. During a particular time period, the workload at the storage group is monitored, and the number and types of cross-data-store operations is determined. The results of the monitoring are used to determine a billing amount for the client based on a selected pricing policy.

Abstract: A remote distributed data store may be configured to process data updates received through invocation of a common API with reference to a common schema. A local data store may also be configured to process updates through the common API with reference to the common schema. Updates to the local data store may be mapped from the local data store schema to the common schema, and applied to the distributed data store. Updates to the distributed data store may be mapped from the common schema to the local data store schema. User identity may be verified to limit data synchronization to authorized users.

Abstract: A remote distributed data store may be configured to process data updates received through invocation of a common API with reference to a common schema. Local data stores may also be configured to process updates using a common API and schema. Data for multiple users may be stored in a common collection of items maintained by a remote distributed data store. User identity may be verified through a public identity service. User identity and access permissions may be associated with items stored in a remote distributed data store.

Abstract: Based at least in part on an optimization goal determined for a storage group comprising a plurality of data stores for which writes requests are coordinated by a log-based transaction manager, one or more lifecycle transitions are identified for data objects stored in a first data store. In accordance with a first lifecycle transition, a data object is to be transferred from the first data store to a second data store based at least in part on a duration for which the data object has been resident at the first data store. A transition agent is assigned by a configuration manager to implement the first lifecycle transition.