US-12619630-B2 - Systems and methods for staging of data updates to database system in a multi-tenant system

US12619630B2US 12619630 B2US12619630 B2US 12619630B2US-12619630-B2

Abstract

The multi-tenant system includes one or more hardware processors that extract standard fields from one or more objects stored in source database systems, the standard fields defining standard subscription attributes. The hardware processors map the standard fields to records within a destination database system, obtain customized fields defining tenant-selected subscription attributes, obtain a mapping of the customized fields to the records; append the standard fields to the customized fields to form appended fields; schedule a pipeline to ingest the appended fields into the records within the destination database system, and ingest the appended fields into the records within the destination database system in order to stage the appended fields into the destination database system.

Inventors

Sai Ram Rakesh Gorenta
Manikandan Chockalingam
Jingjing Pang
Qiang Wu
Yi Feng

Assignees

ZUORA, INC.

Dates

Publication Date: 20260505
Application Date: 20240710

Claims (18)

1 . A multi-tenant system, comprising: one or more hardware processors; and memory storing computer instructions, wherein the computer instructions, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations comprising: extracting one or more standard fields from one or more objects stored in one or more source database systems, the standard fields defining standard subscription attributes; mapping the one or more standard fields to one or more records within a destination database system, wherein the one or more records comprise columns or rows within a table, and wherein mapping the one or more standard fields to the one or more records comprises selecting a particular table within the destination database system into which a particular standard field of the standard fields is ingested based on a classification of the particular standard field, wherein the classification is indicative of a vesting status corresponding to the standard field, the vesting status indicating whether the particular standard field corresponds to a vesting event; obtaining one or more customized fields, the one or more customized fields defining tenant-selected subscription attributes; obtaining a mapping of the one or more customized fields to the one or more records; appending the one or more standard fields to the one or more customized fields to form appended fields; scheduling a pipeline to ingest the appended fields into the one or more records within the destination database system; and ingesting the appended fields into the one or more records within the destination database system in order to stage the appended fields into the destination database system.
2 . The multi-tenant system of claim 1 , wherein the mapping of the one or more standard fields to the one or more records based on the classification comprises mapping a standard field to a staging table if the standard field corresponds to a vesting event and mapping the standard field to a pre-staging table if the standard field corresponds to a nonvesting event.
3 . The multi-tenant system of claim 1 , wherein the one or more standard fields comprise one or more first standard fields, the one or more customized fields comprise one or more first customized fields, the one or more first standard fields corresponding to a first event of a first event type, the one or more records comprises one or more first records; and the computer instructions when executed by the one or more hardware processors are further configured to perform: extracting one or more second standard fields corresponding to a second event from one or more source database systems, the second event being of a second event type; and mapping the one or more second standard fields to one or more second records within the destination database system, and wherein the scheduling of the pipeline comprises partitioning the appended first fields and the one or more second standard fields based on different event types.
4 . The multi-tenant system of claim 3 , wherein the scheduling of the pipeline comprises partitioning the appended first fields into a separate partition as the one or more second standard fields.
5 . The multi-tenant system of claim 1 , wherein the one or more records comprise a row or a column.
6 . The multi-tenant system of claim 1 , wherein the instructions when executed by the one or more hardware processors are further configured to perform: normalizing the extracted one or more standard fields and the obtained one or more customized fields according to a standardized format compatible with the destination database system.
7 . The multi-tenant system of claim 1 , wherein the destination database system is configured to recognize events based on the ingested appended fields and perform workflow operations based on the recognized events.
8 . The multi-tenant system of claim 7 , wherein the one or more customized fields are included in an output of the performed workflow operations.
9 . A method implemented by a multi-tenant system comprising a plurality of computers, the method comprising: extracting one or more standard fields from one or more objects stored in one or more source database systems, the standard fields defining standard subscription attributes; mapping the one or more standard fields to one or more records within a destination database system, wherein the one or more records comprises columns or rows within a table, and wherein mapping the one or more standard fields to the one or more records comprises selecting a particular table within the destination database system into which a particular standard field of the standard fields is ingested based on a classification of the particular standard field, wherein the classification is indicative of a vesting status corresponding to the standard field, the vesting status indicating whether the particular standard field corresponds to a vesting event; obtaining one or more customized fields, the one or more customized fields defining tenant-selected subscription attributes; obtaining a mapping of the one or more customized fields to the one or more records; appending the one or more standard fields to the one or more customized fields to form appended fields; scheduling a pipeline to ingest the appended fields into the one or more records within the destination database system; and ingesting the appended fields into the one or more records within the destination database system in order to stage the appended fields into the destination database system.
10 . The method of claim 9 , wherein the mapping of the one or more standard fields to the one or more records based on the classification comprises mapping a standard field to a staging table if the standard field corresponds to a vesting event and mapping the standard field to a pre-staging table if the standard field corresponds to a nonvesting event.
11 . The method of claim 9 , wherein the one or more standard fields comprise one or more first standard fields, the one or more customized fields comprise one or more first customized fields, the one or more first standard fields corresponding to a first event of a first event type, the one or more records comprises one or more first records; and the method further comprises: extracting one or more second standard fields corresponding to a second event from one or more source database systems, the second event being of a second event type; and mapping the one or more second standard fields to one or more second records within the destination database system, and wherein the scheduling of the pipeline comprises partitioning the appended first fields and the one or more second standard fields based on different event types.
12 . The method of claim 11 , wherein the scheduling of the pipeline comprises partitioning the appended first fields into a separate partition as the one or more second standard fields.
13 . The method of claim 9 , wherein the one or more records comprise a row or a column.
14 . The method of claim 9 , further comprising: normalizing the extracted one or more standard fields and the obtained one or more customized fields according to a standardized format compatible with the destination database system.
15 . The method of claim 9 , further comprising: recognizing, by the destination database system, events based on the ingested appended fields and performing workflow operations based on the recognized events.
16 . The method of claim 15 , wherein the one or more customized fields are included in an output of the performed workflow operations.
17 . A multi-tenant system, comprising: one or more hardware processors; and memory storing computer instructions, wherein the computer instructions, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations comprising: extracting one or more standard fields from one or more objects stored in one or more source database systems, the standard fields defining standard subscription attributes; mapping the one or more standard fields to one or more records within a destination database system; obtaining one or more customized fields, the one or more customized fields defining tenant-selected subscription attributes; obtaining a mapping of the one or more customized fields to the one or more records; appending the one or more standard fields to the one or more customized fields to form appended fields; scheduling a pipeline to ingest the appended fields into the one or more records within the destination database system; and ingesting the appended fields into the one or more records within the destination database system in order to stage the appended fields into the destination database system, wherein the destination database system is configured to recognize events based on the ingested appended fields and to perform workflow operations based on the recognized events.
18 . A method implemented by a multi-tenant system comprising a plurality of computers, the method comprising: extracting one or more standard fields from one or more objects stored in one or more source database systems, the standard fields defining standard subscription attributes; mapping the one or more standard fields to one or more records within a destination database system; obtaining one or more customized fields, the one or more customized fields defining tenant-selected subscription attributes; obtaining a mapping of the one or more customized fields to the one or more records; appending the one or more standard fields to the one or more customized fields to form appended fields; scheduling a pipeline to ingest the appended fields into the one or more records within the destination database system; ingesting the appended fields into the one or more records within the destination database system in order to stage the appended fields into the destination database system; and recognizing, by the destination database system, events based on the ingested appended fields and performing workflow operations based on the recognized events.

Description

CROSS-REFERENCE TO OTHER APPLICATIONS The present application incorporates by reference U.S. Pat. No. 11,409,586, entitled “Extending Data Model of Monolithic Database Through a Microservice for a Multi-Tenant Platform.” TECHNICAL FIELD This disclosure pertains to streamlining staging of data updates to a database system within a multi-tenant system. BACKGROUND Within a multi-tenant system, different database systems may perform specialized functions. For example, a booking database system may record and manage new subscriptions and/or modifications to existing subscriptions. A billing database system may generate invoices, memos, and related items for subscriptions. A revenue database system may recognize, categorize, and report revenue based on accounting rules and according to updates within the booking database system and the billing database system. Updates within the billing database system and the booking database system are staged within the revenue database system. Because of different data shapes of different types of subscription events and different client requirements, a method of streamlining staging of data updates between the different database systems is needed. SUMMARY A claimed solution rooted in computer technology overcomes problems specifically arising in the realm of computer technology. Embodiments of the present invention implement a staging system, within a multi-tenant system, that efficiently streamlines staging of updates, such as subscription related data updates, from booking and/or billing database systems to one or more revenue database systems. Staging may refer to pushing of relevant data fields to a staging area (e.g., a staging table or other table) of the revenue database system or other database system. Currently, bottlenecks exist in staging updates to the revenue database system. For example, some current implementations rely on the revenue database system pulling data from the booking and/or billing database systems. These implementations have limitations, including heavy transformation logic being required to track data from the booking and/or billing database systems to the revenue database system. These implementations may also result in more data being pulled than necessary for the revenue database system. Another limitation is that these implementations are largely a synchronous process. The requirement for the revenue database system to pull data from the booking and/or billing database systems means that the revenue database system may be restricted from performing other workflow tasks, which decreases efficiency of the entire multi-tenant system. These implementations may also cause violation of an accounting principle, specifically, the segregation of duties of Accounting Standards Codification (ASC) 606 because the revenue database system is responsible for revenue recognition as well as booking generation. Additionally, potential inconsistencies of data between the billing database system and the booking database system may not be resolvable by the revenue database system. Embodiments of the present invention overcome these bottlenecks. Embodiments of the present invention implement a staging system that obtains booking and/or billing updates, extracts a subset of relevant fields from the booking and/or billing updates, and stages the subset of relevant fields within particular records of the revenue database system. The booking and/or billing updates may be manifested as booking and/or billing transaction objects within the booking and/or billing database systems. The staging system may define a mapping, such as a schema mapping, from the relevant fields within the booking and/or billing transaction objects to records within the revenue database system. In some embodiments, the records may include a table, a row, and/or a column, and/or correspond to particular locations, addresses, and/or identifiers of the revenue database system. The staging system ingests the subset of relevant fields to the records within the revenue database system based on the mapping. Because of the mapping, the staging system provides relevant updates to the revenue database system in near real-time. Additionally, the mapping enables the subset of relevant fields to be pushed into specific records of the revenue database system. This avoids the revenue database system needing to additionally map the relevant fields into the correct records, and expedites the execution of workflows within the revenue database system. Because of this mapping, the staging system may provide relevant updates to the revenue database system in near real-time according to any data updates arising within any of the booking and/or billing database systems. The staging system extracts the relevant fields, and automatically pushes the extracted fields to the mapped records within the revenue database system in near real-time. In some embodiments, the different records, or groups of records, within the reve