Abstract: Systems and methods are provided for replication sequencing and state management in a distributed storage system. A storage system may receive, from a remote storage system, a request to replicate first tag data for a data object replicated from the remote storage system to the storage system, wherein the first tag data is associated with a request sequence identifier; evaluate an object marker in object metadata for the data object, the object marker comprising an object marker sequence identifier associated with replication of second tag data previously stored for the data object; determine, based on an analysis of the request sequence identifier and the object marker sequence identifier, whether to replace the second tag data with the first tag data, wherein tag data replacement is prohibited if the object marker sequence identifier is after the request sequence identifier; and perform a storage operation associated with the data object.

Abstract: A system performs operations that include receiving a database request to access, via a first connection in a connection pool, information stored in a database of the system. The first connection is associated with a physical connection layer and one or more logical connection layers. The physical connection layer points to a first network socket. Additionally, the operations include storing metadata associated with the one or more logical connection layers in a buffer. The operations further include responsive to determining that the first connection has been terminated and while maintaining the one or more logical layers, modifying the physical connection layer to point to a second network socket that is different from the first network socket. The operations also include subsequent to the modifying, processing the database request via the first connection based on the metadata stored in the buffer.

Abstract: Systems and methods are provided for durable asynchronous replication in a distributed storage system. A storage system may commit a transaction comprising saving a data object to a persistent object storage location and saving a replication marker to a first persistent storage directory for pending replication tasks, wherein the replication marker comprises replication data for replicating the data object to a remote storage system, and wherein the first persistent storage directory comprises a replication queue; determine, based on a presence of the replication marker in the first persistent storage directory, to dequeue the replication marker from the replication queue; move the replication marker to a second persistent storage directory for in-process replication tasks; attempt replication of the data object to the remote storage system; and move the replication marker to a third persistent storage directory.

Abstract: A system performs operations that include receiving a database request to access, via a first connection in a connection pool, information stored in a database of the system. The first connection is associated with a physical connection layer and one or more logical connection layers. The physical connection layer points to a first network socket. Additionally, the operations include storing metadata associated with the one or more logical connection layers in a buffer. The operations further include responsive to determining that the first connection has been terminated and while maintaining the one or more logical layers, modifying the physical connection layer to point to a second network socket that is different from the first network socket. The operations also include subsequent to the modifying, processing the database request via the first connection based on the metadata stored in the buffer.

Abstract: A system performs operations that include receiving a database request to access, via a first connection in a connection pool, information stored in a database of the system. The first connection is associated with a physical connection layer and one or more logical connection layers. The physical connection layer points to a first network socket. Additionally, the operations include storing metadata associated with the one or more logical connection layers in a buffer. The operations further include responsive to determining that the first connection has been terminated and while maintaining the one or more logical layers, modifying the physical connection layer to point to a second network socket that is different from the first network socket. The operations also include subsequent to the modifying, processing the database request via the first connection based on the metadata stored in the buffer.

Abstract: Techniques are disclosed relating to processing database transactions that include application operations defined by different object relational mapping (ORM) libraries. A transaction router module executing on a computer system receives, from an application, a request for a first database transaction, where the first database transaction includes first and second application operations. The transaction router module then translates the first application operation to one or more first database operations using a first ORM library and the second application operation to one or more second database operations using a second ORM library. Then, the transaction router module determines one or more database connections for the one or more first database operations and the one or more second database operations. Such techniques may advantageously allow applications to switch between using different persistence frameworks and message broker frameworks without substantial adjustments to application code.

Abstract: Responsive to a configuration event, a controller instance generates, according to a current version of a configuration interface between the controller instance and a data instance, a configuration message. The configuration message is obtained, via message service, by remote data instances. The remote data instances attempt to process the configuration message, according to whichever version of the configuration interface the respective data instances are using. Appropriate acknowledgements (based on whether the remote data instances could fully process the configuration message or not) are generated and returned to the controller instance that marks a record for the configuration message as complete for the remote instance or marks the record for the configuration message to be re-sent for the remote instance. After waiting some period of time to allow data instances with out-of-date versions to update, a configuration message update cycle re-sends the message to the appropriate remote data instances.

Abstract: A method includes calculating first connection usage information based on a first number of connections being used in a connection pool over a first time interval and adding a first number of database connections to the connection pool based on determining that the first connection usage information satisfies a first usage threshold. Additionally, the method includes calculating second connection usage information based on a second number of connections being used in the connection pool over a second interval. The second interval has been previously reset responsive to adding the first number of database connections to the connection pool. The method also includes determining whether to adjust the number of database connections in the connection pool based on the second connection usage information.

Abstract: Techniques are disclosed relating to processing database transactions that include application operations defined by different object relational mapping (ORM) libraries. A transaction router module executing on a computer system receives, from an application, a request for a first database transaction, where the first database transaction includes first and second application operations. The transaction router module then translates the first application operation to one or more first database operations using a first ORM library and the second application operation to one or more second database operations using a second ORM library. Then, the transaction router module determines one or more database connections for the one or more first database operations and the one or more second database operations. Such techniques may advantageously allow applications to switch between using different persistence frameworks and message broker frameworks without substantial adjustments to application code.

Abstract: Techniques are disclosed relating to processing database transactions that include application operations defined by different object relational mapping (ORM) libraries. A transaction router module executing on a computer system receives, from an application, a request for a first database transaction, where the first database transaction includes first and second application operations. The transaction router module then translates the first application operation to one or more first database operations using a first ORM library and the second application operation to one or more second database operations using a second ORM library. Then, the transaction router module determines one or more database connections for the one or more first database operations and the one or more second database operations. Such techniques may advantageously allow applications to switch between using different persistence frameworks and message broker frameworks without substantial adjustments to application code.

Abstract: A method includes calculating first connection usage information based on a first number of connections being used in a connection pool over a first time interval and adding a first number of database connections to the connection pool based on determining that the first connection usage information satisfies a first usage threshold. Additionally, the method includes calculating second connection usage information based on a second number of connections being used in the connection pool over a second interval. The second interval has been previously reset responsive to adding the first number of database connections to the connection pool. The method also includes determining whether to adjust the number of database connections in the connection pool based on the second connection usage information.

Abstract: A system performs operations that include receiving a database request to access, via a first connection in a connection pool, information stored in a database of the system. The first connection is associated with a physical connection layer and one or more logical connection layers. The physical connection layer points to a first network socket. Additionally, the operations include storing metadata associated with the one or more logical connection layers in a buffer. The operations further include responsive to determining that the first connection has been terminated and while maintaining the one or more logical layers, modifying the physical connection layer to point to a second network socket that is different from the first network socket. The operations also include subsequent to the modifying, processing the database request via the first connection based on the metadata stored in the buffer.

Abstract: A system performs operations that include receiving a database request to access, via a first connection in a connection pool, information stored in a database of the system. The first connection is associated with a physical connection layer and one or more logical connection layers. The physical connection layer points to a first network socket. Additionally, the operations include storing metadata associated with the one or more logical connection layers in a buffer. The operations further include responsive to determining that the first connection has been terminated and while maintaining the one or more logical layers, modifying the physical connection layer to point to a second network socket that is different from the first network socket. The operations also include subsequent to the modifying, processing the database request via the first connection based on the metadata stored in the buffer.

Abstract: A method includes calculating first connection usage information based on a first number of connections being used in a connection pool over a first time interval and adding a first number of database connections to the connection pool based on determining that the first connection usage information satisfies a first usage threshold. Additionally, the method includes calculating second connection usage information based on a second number of connections being used in the connection pool over a second interval. The second interval has been previously reset responsive to adding the first number of database connections to the connection pool. The method also includes determining whether to adjust the number of database connections in the connection pool based on the second connection usage information.

Abstract: Techniques are disclosed relating to processing database transactions that include application operations defined by different object relational mapping (ORM) libraries. A transaction router module executing on a computer system receives, from an application, a request for a first database transaction, where the first database transaction includes first and second application operations. The transaction router module then translates the first application operation to one or more first database operations using a first ORM library and the second application operation to one or more second database operations using a second ORM library. Then, the transaction router module determines one or more database connections for the one or more first database operations and the one or more second database operations. Such techniques may advantageously allow applications to switch between using different persistence frameworks and message broker frameworks without substantial adjustments to application code.

Abstract: A system performs operations that include receiving a database request to access, via a first connection in a connection pool, information stored in a database of the system. The first connection is associated with a physical connection layer and one or more logical connection layers. The physical connection layer points to a first network socket. Additionally, the operations include storing metadata associated with the one or more logical connection layers in a buffer. The operations further include responsive to determining that the first connection has been terminated and while maintaining the one or more logical layers, modifying the physical connection layer to point to a second network socket that is different from the first network socket. The operations also include subsequent to the modifying, processing the database request via the first connection based on the metadata stored in the buffer.

Abstract: A method includes calculating first connection usage information based on a first number of connections being used in a connection pool over a first time interval and adding a first number of database connections to the connection pool based on determining that the first connection usage information satisfies a first usage threshold. Additionally, the method includes calculating second connection usage information based on a second number of connections being used in the connection pool over a second interval. The second interval has been previously reset responsive to adding the first number of database connections to the connection pool. The method also includes determining whether to adjust the number of database connections in the connection pool based on the second connection usage information.

Abstract: A method and a system to manage recommendations in an online marketplace are presented. A social shopping interface is provided at a publisher site accessed by a first user identified by a first user identifier. A recommendation of a listing describing an item for sale and including a second user identifier corresponding to a second user is accessed from a recommendation database. The recommendation, including at least a portion of the listing and the second user identifier are displayed to the first user at the publisher site via the social shopping interface.

Abstract: A method and a system to manage recommendations in an online marketplace are presented. A social shopping interface is provided at a publisher site accessed by a first user identified by a first user identifier. A recommendation of a listing describing an item for sale and including a second user identifier corresponding to a second user is accessed from a recommendation database. The recommendation, including at least a portion of the listing and the second user identifier are displayed to the first user at the publisher site via the social shopping interface.

Abstract: A method and a system to manage recommendations in an online marketplace are presented. A social shopping interface is provided at a publisher site accessed by a first user identified by a first user identifier. A recommendation of a listing describing an item for sale and including a second user identifier corresponding to a second user is accessed from a recommendation database. The recommendation, including at least a portion of the listing and the second user identifier are displayed to the first user at the publisher site via the social shopping interface.