Abstract: Systems and methods are provided for managing a distributed database across multiple cloud provider systems. Database elements (e.g., primary, secondary, and/or read-only nodes) are distributed across multiple cloud provider systems. A provisioning component is configured to enable cross-cloud configuration options to specify the manner in which the clusters/replica set members are to be deployed across multiple cloud providers and/or geographical regions.

Abstract: Methods and system implement solutions for integrating encryption and emulation into native database formats and/or architectures. “Native” database is used to describe a database that has not been designed for end to end encryption, an off the shelf database deployment, and/or a commercially available database. According to some embodiments, various encryption systems and methods employ emulation operations to enable a native database and native database functions to leverage full encryption primitives. Various aspects integrate emulation operations into standard database implementations, where the emulation enables native database functions to operate on entirely encrypted data.

Abstract: Systems and methods are configured to identify and resolve user-based issues, architecture issues, and data model issues that are introduced into distributed database deployments. Even in the context of a pre-built distributed database system, “bad” user behavior can have huge impacts on database performance. Various embodiments provide for analysis and resolution of architecture issues, as well schema issues, and can be configured to identify and resolve such problems in the context of dynamic schema database systems. Unlike relational database counterparts, dynamic schema databases do not enforce static database architecture or defined schemas. In such environments, database data and database formatting can be mostly unconstrained. If used properly, this flexibility enables easy configuration and execution. However, when improperly designed, small flaws magnify in significance as the database grows.

Abstract: Methods and system implement solutions for integrating encryption and emulation into native database formats and/or architectures. “Native” database is used to describe a database that has not been designed for end to end encryption, an off the shelf database deployment, and/or a commercially available database. According to some embodiments, various encryption systems and methods employ emulation operations to enable a native database and native database functions to leverage full encryption primitives. Various aspects integrate emulation operations into standard database implementations, where the emulation enables native database functions to operate on entirely encrypted data.

Abstract: Systems and methods are configured to identify and resolve user-based issues, architecture issues, and data model issues that are introduced into distributed database deployments. Even in the context of a pre-built distributed database system, “bad” user behavior can have huge impacts on database performance. Various embodiments provide for analysis and resolution of architecture issues, as well schema issues, and can be configured to identify and resolve such problems in the context of dynamic schema database systems. Unlike relational database counterparts, dynamic schema databases do not enforce static database architecture or defined schemas. In such environments, database data and database formatting can be mostly unconstrained. If used properly, this flexibility enables easy configuration and execution. However, when improperly designed, small flaws magnify in significance as the database grows.

Abstract: A method is provided for resharding a sharded database sharded according to a first shard key. The method includes: receiving, by a processor an instruction to reshard the sharded database; receiving, at the processor, a new shard key to be used in a resharding process to reshard the sharded database; determining, by the processor, whether a duration of unavailability of the sharded database during the resharding process is less than a predetermined amount of time; and automatically performing, by the processor, the resharding process according to the new shard key to produce a resharded database, if the duration of unavailability is less than the predetermined amount of time. The method may be performed without users noticing a significant interruption to read/write operations from/to the database.

Abstract: A database system may use asymmetric hardware for analytics nodes. In some embodiments, a database system includes a replica set comprising a plurality of base nodes and at least one analytics node. The analytics nodes may have asymmetric hardware respective to the base nodes. The base nodes may include a primary node and two secondary nodes. The primary node may be configured to accept writes and propagate the writes to secondary nodes and may also propagate writes to analytics nodes. Secondary nodes may replicate writes and accept reads. Analytics nodes may perform data analysis operations. Analytics nodes may have a first instance size different than a second instance size of the base nodes.

Abstract: In some embodiments, a database cluster to cluster synchronization system may include multiple replicators coupled to a source database cluster and a destination database cluster, where the source and destination cluster may be shard clusters. Each of the multiple replicators may correspond to a respective subset of the source database cluster and configured to monitor changes of data on the respective subset of the source database cluster and translate the changes of data to one or more database operations to be performed on the destination cluster. The changes of data on the source database may be contained in respective change streams associated with each of the replicators.

Abstract: Described herein are techniques optimizing queries on data in a data lake. The techniques involve ingesting data from multiple data lake sources, partitioning the data based on a key, and generating a partition index based on the key. The partition index can then be used to efficiently perform queries on data in the data lake.

Abstract: In some embodiments, a database cluster to cluster synchronization system may include multiple replicators coupled to a source database cluster and a destination database cluster, where the source and destination cluster may be shard clusters. Each of the multiple replicators may correspond to a respective subset of the source database cluster and configured to monitor changes of data on the respective subset of the source database cluster and translate the changes of data to one or more database operations to be performed on the destination cluster. The changes of data on the source database may be contained in respective change streams associated with each of the replicators.

Abstract: A database system comprising a database having a dynamic schema and at least one processor configured to: generate at least one column store index associated with the database, at least by: extracting keys from at least one document in the database, and sorting the keys; store the at least one column store index at least by storing the keys in the database; and access the at least one column store index based on at least one access request.

Abstract: A database system comprising a database comprising a plurality of data storage nodes, the plurality of data storage nodes including a primary storage node and a plurality of secondary storage nodes. The database system may also include at least one processor configured to: perform at least one write command to a secondary storage node of the plurality of secondary storage nodes; and perform at least one backup command, at least partially in parallel with the at least one write command being performed to the secondary storage node, of at least some data from a snapshot of data stored in the secondary storage node. A method for performing at least one backup command in a database at least partially in parallel with the at least one write command being performed.

Abstract: Systems, methods, and computer-readable media provide techniques for on-demand access to object data hosted in distributed object storage. A query is received for the distributed object storage database, wherein the distributed object storage database includes first object data stored in a first data center at a first geographical location, and second object data stored in a second data center at a second geographical location. It is determined that the query is for at least a portion of the first object data stored by the first data center. The query is transmitted to a first computing device in the first data center. Results are received from the first computing device for the query, and the results are provided in response to the received query.

Abstract: According to some aspects, provided are systems and methods that implement end-to-end encryption, and provide implementation configured to secure information during execution of queries on an encrypted data source. Various embodiments include multiple encrypted multi-map data structures and associated encryption schemes configured to securely read, write, and delete information while supporting any one or more of the following features: snapshot security, multiple client support, efficient execution under concurrent operation, and resilience to client failures. In various embodiments, addressable multi-map data structures enable concurrent access, and allow correct operation under polynomial time constraints.

Abstract: Systems and methods are provided for managing a distributed database across multiple cloud provider systems. Database elements (e.g., primary, secondary, and/or read-only nodes) are distributed across multiple cloud provider systems. A provisioning component is configured to enable cross-cloud configuration options to specify the manner in which the clusters/replica set members are to be deployed across multiple cloud providers and/or geographical regions.

Abstract: According to some aspects, provided are systems and methods that implement end-to-end encryption, and provide implementation configured to secure information during execution of queries on an encrypted data source. Various embodiments include multiple encrypted multi-map data structures and associated encryption schemes configured to securely read, write, and delete information while supporting any one or more of the following features: snapshot security, multiple client support, efficient execution under concurrent operation, and resilience to client failures. In various embodiments, addressable multi-map data structures enable concurrent access, and allow correct operation under polynomial time constraints.

Abstract: According to some aspects, provided are systems and methods that implement end-to-end encryption, and provide implementation configured to secure information during execution of queries on an encrypted data source. Various embodiments include multiple encrypted multi-map data structures and associated encryption schemes configured to securely read, write, and delete information while supporting any one or more of the following features: snapshot security, multiple client support, efficient execution under concurrent operation, and resilience to client failures. In various embodiments, addressable multi-map data structures enable concurrent access, and allow correct operation under polynomial time constraints.

Abstract: A method for managing data synchronization for a database having a dynamic schema, the method comprising: generating, at a first client device, a first changeset that is representative of an operation on a data object in a database; transmitting a synchronization request for synchronizing the database with one or more changesets generated by a second client device; receiving a second changeset that is representative of an operation performed by the second client device on the data object, wherein the database is shared between the first client device and the second client device; and merging, at the first client device, the first changeset and the second changeset to update the data object, wherein the merging is performed based on data received from a plurality of the one or more servers operating in parallel to each other.

Abstract: Described herein are embodiments of a database system for performing multi-document transactions. The database system comprises a database comprising a plurality of data storage nodes. The database system receives transactions that access at least two documents stored in the database. The database system generates a transaction identifier associated with the transaction and associates operations in the transaction with the transaction identifier. The database system performs at least part of the transaction on the database and determines whether an error occurred in performing in performing the transaction. When the database system determines that an error occurred in performing the transaction, the database system reverses any performed operations of the transaction. When no error occurs in performing the transaction, the database system outputs a confirmation.

Abstract: A database system comprising a database having a dynamic schema and comprising a plurality of data storage nodes; and at least one processor configured to, using an encryption process: manage access to plaintext data stored in the plurality of data storage nodes by users employing at least one client-controlled resource in a client access layer; restrict access to the plaintext data by other users, wherein the other users include users with system administration privileges for the database and administrators of processing resources hosting the database; and manage access to encrypted copies of the plaintext data by the users with system administration privileges for the database such that the system administration privileges do not enable access to plaintext versions of the encrypted copies. A method for managing data security for a database. A database system with a dynamic schema architecture, a client access layer, and an operational database layer.