Microservice Custom Attribute Management via Unified Placeholder Tables
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In microservice-based architectures, managing custom attributes and their values for domain objects becomes inefficient due to exponential growth of custom attribute management tables, leading to performance issues such as non-performant searching and sorting.
Innovation Solution
A system and method for generating and managing custom attributes by using a configuration of value tables with placeholder fields within a repository, where custom attributes are mapped to these fields, allowing a single record to store all custom attribute values for a domain object, thereby reducing storage needs and improving performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If custom attributes are managed using separate tables for each domain object, then customization flexibility is improved, but storage space requirements and system complexity increase exponentially
Solution Approach 1:
The patent merges multiple separate custom attribute tables into a single unified custom attribute table. Instead of having separate tables for each domain object's custom attributes, the system uses one consolidated table with columns that can accommodate custom attributes across different domain objects. This reduces the total number of tables and storage space requirements while maintaining the ability to store customized attributes for various domain objects through a standardized structure.
Solution Approach 2:
The unified custom attribute table is designed to serve multiple domain objects simultaneously. The table structure includes generic columns that can represent custom attributes for any domain object type, making the table universal in its functionality. This multi-functional approach allows the same table to store custom attributes for different domain objects without requiring separate specialized tables for each, thereby reducing storage overhead and system complexity.
2Ease of operation
If custom attributes are managed using separate tables for each domain object, then attribute organization is improved, but search and sort performance deteriorates
Solution Approach 1:
By consolidating custom attribute data into a single unified table, the patent improves search and sort performance. The unified structure allows the database engine to optimize queries more effectively compared to multiple scattered tables. Searches and sorts can be performed across all custom attributes in one table rather than requiring complex joins across multiple tables, significantly improving productivity for search and sort operations while maintaining organized attribute management through standardized column definitions.
3Stability of the object's composition
If multiple separate tables are used for custom attributes, then data normalization is improved, but system complexity and maintenance difficulty increase
Solution Approach 1:
The patent reduces system complexity by merging multiple custom attribute tables into one unified table. This consolidation decreases the number of table definitions, relationships, and maintenance operations required. The unified table structure simplifies the schema and reduces the complexity of data management operations while maintaining data normalization principles through proper column organization and data types. Maintenance tasks such as backups, repairs, and updates become simpler with fewer tables to manage.
Data Source
AI summary
In general, various aspects of the present invention provide methods, apparatuses, systems, computing devices, computing entities, and/or the like for generating and managing custom attributes and corresponding values for domain objects defined within microservices. In accordance with various aspects, a method is provided that comprises: receiving a custom attribute request for a domain object defined in a microservice that comprises a domain object identifier, a custom attribute to add to the domain object, and a value type for the custom attribute; identifying, based on the domain object identifier and the value type, a custom value table for the domain object that comprises placeholder fields; identifying a placeholder field that is available in the custom value table; and storing a record in the attribute schema table for the domain object and the custom attribute comprising mapping data that maps the custom attribute to the placeholder field for the custom value table.