Abstract: A method of a data manager for a database management system having a primary database and a staging storage includes receiving a request including identifying information for a set of records that have been sent to the database management system for storage, searching the staging storage for the set of records using the identifying information, and storing the set of records into the primary database prior to a scheduled storage for the set of records based on a general process for ingesting records sent to the database management system for storage in the primary database, in response to the request and to the set of records matching the identifying information.

Abstract: Disclosed are some implementations of systems, apparatus, methods and computer program products for performing data ingestion. A request received from a client device is processed, where the request has a payload including a plurality of data items pertaining to a data object. An identifier associated with the data object is generated. Information including the data items is obtained from the request. The information including the data items is stored in association with the identifier in a first data store, where the first data store is not a relational database. The data items and identifier are obtained from the first data store and stored in a second data store, where the second data store is a relational database. A query including the identifier is processed to obtain the identifier from the query. It is determined whether the identifier obtained from the query is in the first data store.

Abstract: Disclosed embodiments are related to Application Programming Interface (API) technologies, and in particular, to Order APIs that are used to make modifications and cancelations to existing order objects. The Order APIs can be used to retrieve the current state of an order object, retrieve the summarized state of an order object as of a specified date, and retrieve a potential state of an order object along with specified changes. The Order APIs are also used to process order changes including changes to the quantity of an existing order object and applying line item changes to an existing order object. Other embodiments may be described and/or claimed.

Abstract: Methods, systems, and devices supporting data storage are described. A database system may store order information for an organization. This order information may span multiple steps of an order lifecycle, including order creation, order changes, order fulfillment, etc. To efficiently store order information for low-latency querying and data consistency, the database system may implement order summaries. For example, a database server may receive a new order data object associated with an order identifier and may create a corresponding order summary data object. If the database system receives any additional data objects associated with the same order identifier, the database server may update the order summary data object based on the additional data objects. If the database system receives a query for information related to the order, the system may retrieve queried values directly from the order summary data object, rather than aggregating data on-the-fly across multiple underlying data objects.

Abstract: Disclosed are some implementations of systems, apparatus, methods and computer program products for performing data ingestion. A request received from a client device is processed, where the request has a payload including a plurality of data items pertaining to a data object. An identifier associated with the data object is generated. Information including the data items is obtained from the request. The information including the data items is stored in association with the identifier in a first data store, where the first data store is not a relational database. The data items and identifier are obtained from the first data store and stored in a second data store, where the second data store is a relational database. A query including the identifier is processed to obtain the identifier from the query. It is determined whether the identifier obtained from the query is in the first data store.

Abstract: Disclosed embodiments are related to Application Programming Interface (API) technologies, and in particular, to Order APIs that are used to make modifications and cancelations to existing order objects. The Order APIs can be used to retrieve the current state of an order object, retrieve the summarized state of an order object as of a specified date, and retrieve a potential state of an order object along with specified changes. The Order APIs are also used to process order changes including changes to the quantity of an existing order object and applying line item changes to an existing order object. Other embodiments may be described and/or claimed.

Abstract: Methods, systems, and devices supporting data storage are described. A database system may store order information for an organization. This order information may span multiple steps of an order lifecycle, including order creation, order changes, order fulfillment, etc. To efficiently store order information for low-latency querying and data consistency, the database system may implement order summaries. For example, a database server may receive a new order data object associated with an order identifier and may create a corresponding order summary data object. If the database system receives any additional data objects associated with the same order identifier, the database server may update the order summary data object based on the additional data objects. If the database system receives a query for information related to the order, the system may retrieve queried values directly from the order summary data object, rather than aggregating data on-the-fly across multiple underlying data objects.

Abstract: Disclosed are examples of systems, apparatus, methods, and computer program products for processing offline updates to records of a database system. In some implementations, a first update to a record is processed, and the record is modified according to a first action and first data of the first update. A second update to the record from a device with an offline status is processed. It can be determined that the second update and the first update are associated with a same portion of the record. It can be determined that the second timestamp is prior to the first timestamp. A notification can be provided to the device. The record can be modified according to a second action and second data of the second update.

Abstract: Disclosed are examples of systems, apparatus, methods, and computer program products for processing offline updates to records of a database system. In some implementations, a first update to a record is processed, and the record is modified according to a first action and first data of the first update. A second update to the record from a device with an offline status is processed. It can be determined that the second update and the first update are associated with a same portion of the record. It can be determined that the second timestamp is prior to the first timestamp. A notification can be provided to the device. The record can be modified according to a second action and second data of the second update.