Abstract: In some implementations, there is provided a method that includes configuring a first threshold for page-loadable data at a buffer cache associated with a database; checking the buffer cache to determine usage of the buffer cache by the page-loadable data; in response to the usage of the buffer cache being more than the first threshold, causing a background job to release one or more buffers in the buffer cache; checking, after releasing at least one buffer of the buffer cache, the buffer cache to determine whether usage by the page-loadable data is below the first threshold; in response to the usage being below the first threshold, stopping the release of additional one or more buffers in the buffer cache; and in response to the usage being above the first threshold, continuing the release of the additional one or more buffers in the buffer cache.

Abstract: In an example embodiment, a solution is provided for coordinating transactions across both relational databases and open format tables on object storage. This technology addresses the challenge of integrating open table formats, such as Delta and Iceberg, with relational databases like SAP HANA. These technical challenges include subtleties imposed by database transaction isolation, asynchronous parallelism, and dealing with instabilities. More specifically, transactions are broken down a transaction into smaller, independent sub-transactions. Each sub-transaction is executed independently. If a sub-transaction fails, compensating actions are performed to undo its effects. This approach ensures that the overall transaction is applied atomically.

Abstract: A cloud-based data platform is disclosed, enabling storage-agnostic data management and analytics in a unified environment. The system may integrate a data lake implemented as a hyperscaler object store, a cloud-based database management system (DBMS), elastic compute resources, and analytics engines. Data may be stored in open table formats, such as Apache Parquet, Delta Lake, and Apache Iceberg, supporting ACID transactions, schema evolution, and efficient query processing. Virtual tables may map data stored in the data lake to the DBMS, enabling in-situ query processing via SQL interfaces. The platform may support advanced features, including change data capture (CDC), time travel, and lifecycle management using a SAGA pattern for atomic operations. Security may be ensured through X.509 certificates, web tokens, and role-based access controls. Elastic compute resources, such as Apache Spark, facilitate large-scale data transformations and analytics.

Abstract: A database system detects a query targeting a first database object stored in a unified persistence format in a persistence store. In response to detecting the query, the database system determines whether to load the first database object in column-loadable format or page-loadable format into an in-memory store. In response to determining to load the first database object in the column-loadable format, the database system determines if a first bit representation of one or more corresponding primitives in the persistence store is compatible with a second bit representation used for storing the primitives in the in-memory store. The database system performs a native copy operation to copy the primitives from the persistence store to the in-memory store if the bit representations are compatible, where the native copy operation involves copying the primitives on a page-by-page basis without decoding and encoding values of the one or more primitives.

Abstract: A database system detects a query targeting a first database object stored in a unified persistence format in a persistence store, where a first load unit is specified for loading the first database object into an in-memory store. The database system determines whether to convert the first load unit to a second load unit based on one or more conditions. In response to determining to convert the first load unit to the second load unit for the first database object, the first database object is loaded into the in-memory store according to the second load unit without performing a rewrite of the first database object in the persistence store. In an example, the first load unit is a column-loadable unit and the second load unit is a page-loadable unit.

Abstract: A database system detects an operation to move a first database object from an in-memory store to a persistence store, wherein the first database object is in either a page-loadable or column-loadable format in the in-memory store, and wherein the first database object comprises a plurality of subcomponents. Each subcomponent of the first database object is examined separately from other subcomponents of the plurality of subcomponents. In response to determining that a first subcomponent of the plurality of subcomponents has a datatype and a compression type supported by a unified persistence format, the first subcomponent is stored in a unified persistence format in the persistence store. In response to determining that a second subcomponent of the plurality of subcomponents has either a datatype or a compression type which is not supported by the unified persistence format, the second subcomponent is stored in a serial persistence format in the persistence store.

Abstract: A database system detects a query targeting a first database object stored in a unified persistence format in a persistence store, where a first load unit is specified for loading the first database object into an in-memory store. The database system determines whether to convert the first load unit to a second load unit based on one or more conditions. In response to determining to convert the first load unit to the second load unit for the first database object, the first database object is loaded into the in-memory store according to the second load unit without performing a rewrite of the first database object in the persistence store. In an example, the first load unit is a column-loadable unit and the second load unit is a page-loadable unit.

Abstract: A system for managing data persistence formats in a computing system, comprising, at least one data processor; and at least one memory result in operations comprising: computing an estimated serial size (ES) for a dataset; computing an estimated unified size (EU) for the dataset; selecting, based at least in part on a predefined set of rules, between a serial persistence format and a unified persistence format to store the dataset, wherein the selection is based at least in part on the computed estimated serial size and the computed estimated unified size; storing the selected persistence format in a metadata associated with the stored dataset; and in response to a loading request, loading the stored dataset by referring to the metadata.

Abstract: A database system detects a query targeting a first database object stored in a unified persistence format in a persistence store. In response to detecting the query, the database system determines whether to load the first database object in column-loadable format or page-loadable format into an in-memory store. In response to determining to load the first database object in the column-loadable format, the database system determines if a first bit representation of one or more corresponding primitives in the persistence store is compatible with a second bit representation used for storing the primitives in the in-memory store. The database system performs a native copy operation to copy the primitives from the persistence store to the in-memory store if the bit representations are compatible, where the native copy operation involves copying the primitives on a page-by-page basis without decoding and encoding values of the one or more primitives.

Abstract: A database system detects an operation to move a first database object from an in-memory store to a persistence store, wherein the first database object is in either a page-loadable or column-loadable format in the in-memory store, and wherein the first database object comprises a plurality of subcomponents. Each subcomponent of the first database object is examined separately from other subcomponents of the plurality of subcomponents. In response to determining that a first subcomponent of the plurality of subcomponents has a datatype and a compression type supported by a unified persistence format, the first subcomponent is stored in a unified persistence format in the persistence store. In response to determining that a second subcomponent of the plurality of subcomponents has either a datatype or a compression type which is not supported by the unified persistence format, the second subcomponent is stored in a serial persistence format in the persistence store.

Abstract: For each job of a plurality of jobs, a plurality of instances of the job may be generated that are associated with a plurality of subnets of a plurality of regions of an account. Job allocation requests received at a queue may be sequentially processed to determine a respective subnet of a respective region to allocate each job to. The determination may be based on a number of data processing units currently available to the account and one or more subnet conditions of the subnets. Each job may be allocated accordingly to cause an execution of an instance of each job associated with the respective subnet of the respective region. As each job is allocated, a resource status table for the account may be maintained. The table may be updated based on a deallocation request received at the queue subsequent to a completion of each job.

Abstract: In some implementations, there is provided a method that includes configuring a first threshold for page-loadable data at a buffer cache associated with a database; checking the buffer cache to determine usage of the buffer cache by the page-loadable data; in response to the usage of the buffer cache being more than the first threshold, causing a background job to release one or more buffers in the buffer cache; checking, after releasing at least one buffer of the buffer cache, the buffer cache to determine whether usage by the page-loadable data is below the first threshold; in response to the usage being below the first threshold, stopping the release of additional one or more buffers in the buffer cache; and in response to the usage being above the first threshold, continuing the release of the additional one or more buffers in the buffer cache.

Abstract: A primary database system loads database objects into a primary in-memory store according to a given format. The primary database captures, in replay logs, the loading of the database objects according to the given format. The primary database sends the replay logs to a secondary database system. In response to receiving a replay log, the secondary database checks the value of a log replay configuration parameter. If the configuration parameter is a first value, the secondary database replays the replay log to load the corresponding database objects into a secondary in-memory store according to a first format. If the configuration parameter is a second value, the secondary database replays the log to load the objects according to a second format, and if the configuration parameter is a third value, the secondary database replays the log to load the objects in a same format which was used by the primary database.

Abstract: A database system detects a query targeting a first database object stored in a unified persistence format in a persistence store. In response to detecting the query, the database system determines whether to load the first database object in column-loadable format or page-loadable format into an in-memory store. In response to determining to load the first database object in the column-loadable format, the database system determines if a first bit representation of one or more corresponding primitives in the persistence store is compatible with a second bit representation used for storing the primitives in the in-memory store. The database system performs a native copy operation to copy the primitives from the persistence store to the in-memory store if the bit representations are compatible, where the native copy operation involves copying the primitives on a page-by-page basis without decoding and encoding values of the one or more primitives.

Abstract: A system and method including receiving a request to update a timestamp associated with database pages of a database instance logically organized into at least one page set, each of the at least one page set including a plurality of the database pages; updating the timestamp associated with each database page in each respective at least one page set; issuing, in response to updating the timestamp associated with a last database page in each of the at least one page set, a write request to write the plurality of database pages in each of the respective at least one page set to a persistent data store; and writing the plurality of database pages in each of the respective at least one page set to a persistent data store, the plurality of database pages written to the persistent data store having an updated timestamp associated therewith.

Abstract: A system and method including receiving a request to update a timestamp associated with database pages of a database instance logically organized into at least one page set, each of the at least one page set including a plurality of the database pages; updating the timestamp associated with each database page in each respective at least one page set; issuing, in response to updating the timestamp associated with a last database page in each of the at least one page set, a write request to write the plurality of database pages in each of the respective at least one page set to a persistent data store; and writing the plurality of database pages in each of the respective at least one page set to a persistent data store, the plurality of database pages written to the persistent data store having an updated timestamp associated therewith.

Abstract: According to some embodiments, a system, method and non-transitory, computer readable medium are provided comprising a memory storing processor-executable program code; and a processing unit to cause the system to: receive a range of persistent volume disk size values from a cloud service provider; receive a value for an upper bound of a number of persistent volume disks attachable to a virtual machine per the cloud service; determine a number of persistent volume disks based on the upper bound, wherein the number is at least two; generate a plurality of configurations of the determined number of persistent volume disks, wherein a configuration is provided for each persistent volume disk size value, and each configuration divides the persistent volume disk size value between two or more persistent volume disks; and aggregate the generated plurality of configurations in a decision table. Numerous other aspects are provided.

Abstract: Among the various aspects of the present disclosure is the provision of methods, synthetic DC, and compositions for T cell activation. The present disclosure provides for synthetic dendritic cells (DCs), methods of generating synthetic dendritic cells (DCs), methods of generating T cell-encapsulated gelatin microspheres and microcapsules, methods of activating T cells using synthetic DCs, methods for expanding T cells against individualized antigen-specific mutational antigens using synthetic DCs, and methods of treating a chronic disease (e.g., HIV, HPV) or cancer using the synthetic DCs.

Abstract: Disclosed herein are system, method, and computer-program product embodiments for generating a paged and in-memory representation of a database object. An embodiment operates by maintaining in-memory and paged form primitives unique to the database object or a substructure thereof in a database such that the in-memory and paged form primitives are capable of providing the in-memory and paged representations of the database objects, respectively. Thereafter, a load configuration for the database object is determined. Based on the load configuration, the in-memory and/or paged representations of the database object are generated using the in-memory form primitive or the paged form primitive unique to the database object, respectively. Subsequently, the in-memory and/or paged representations of the database object are stored in the database.

Abstract: Among the various aspects of the present disclosure is the provision of a hydrogel-based substrate comprising an aldehyde-containing component, such as N-ethanal acrylamide. The hydrogel component allows for functionalization of a hydrogel through conjugation of proteins (e.g., collagen) to the hydrogel in the absence of a post hoc crosslinking component.