Standard Object Replication for Stable Custom Views
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data processing systems face challenges in efficiently managing changes to standard objects without disrupting customer-defined views, leading to potential disruptions in data retrieval and manipulation, especially in scenarios involving database schema alterations and message streaming systems.
Innovation Solution
A system that utilizes a replication object to capture changes to standard objects without storing actual data, generating change logs, and transmitting them to a message bus, ensuring synchronization between the standard object and customer-defined views, thereby maintaining integrity and enabling real-time updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the maintainer changes the structure of a standard object (add/drop/change columns), then the product can be improved and defects can be fixed, but the customer's integration may break and the public API may be disrupted
Solution Approach 1:
The patent segments the object model into standard objects (maintained by the provider) and custom objects (created by customers based on their needs). This segmentation allows the maintainer to modify standard objects without forcing customers to change their integrations, as customers can define their own custom objects that reference the standard objects. The contradiction is resolved by allowing independent evolution of standard and custom objects.
Solution Approach 2:
The patent introduces dynamic versioning and evolution capabilities where standard objects can change over time while maintaining backward compatibility. The system dynamically manages relationships between standard and custom objects, allowing the maintainer to add or remove columns from standard objects while customers' custom objects continue to function. This dynamic approach resolves the contradiction by enabling continuous product improvement while maintaining integration stability.
2Productivity
If direct SQL access is provided to customers for rigid table schemas, then data access is efficient and well-defined, but any schema change requires customers to change their code
Solution Approach 1:
The patent introduces custom objects as an intermediary layer between customers and the underlying database schemas. Instead of customers directly accessing rigid table schemas through SQL, they interact with flexible custom objects that can adapt to schema changes. This intermediary allows efficient data access while providing adaptability, as the custom objects can be modified to reflect schema changes without requiring customers to change their code.
Solution Approach 2:
The patent allows customers to create custom objects that are essentially copies or projections of standard objects, tailored to their specific needs. These custom objects capture the essential data structure and behavior that customers need, while decoupling them from the underlying schema. When the schema changes, the custom objects can remain unchanged or be selectively updated, resolving the contradiction between data access efficiency and schema change flexibility.
3Reliability
If versioning is implemented for APIs, then old versions can be supported for a period, but customers still need to update their code to adopt new versions
Solution Approach 1:
The patent enables customers to define custom objects in advance based on their specific requirements, rather than being forced to adapt to provider-defined versions. This preliminary action allows customers to establish their own data access patterns that are independent of API versions. When schema changes occur, customers don't need to update their code because their custom objects were designed to be adaptable from the start, eliminating the time loss associated with code updates while maintaining reliability.
4Reliability
If a customer creates views to represent old and new objects, then some compatibility can be maintained, but the provider must create and maintain the new view to avoid breaking the object definitions
Solution Approach 1:
The patent empowers customers to define and maintain their own custom objects that serve as their personal views of the data, rather than relying on the provider to create and maintain views. This self-service approach allows customers to tailor the data representation to their specific needs and maintain it independently. The provider no longer needs to create and maintain multiple views for different customer scenarios, significantly reducing the complexity of view maintenance while maintaining or improving compatibility.
Data Source
AI summary
Techniques are described herein for efficiently managing and transmitting changes to a standard object within a data processing system while preserving the integrity of customer-defined custom views on that standard object. The proposed systems and methods introduce a novel approach to handling Create, Update, and Destroy (hereinafter “CUD”) operations on a standard object, allowing customers to define custom views that encapsulate specific fields of interest. The systems and methods involve the creation of a replication object, triggered by changes to the standard object, which captures these alterations without storing actual data. This mechanism, coupled with the generation of change logs and transmission to a message bus, enables changes to the standard object to be performed without impacting the customer-defined views.