Database Schema Management for Micro-service Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Micro-service architecture faces challenges in integrating components with different runtimes and database schemas, leading to deployment dependencies and name collisions, which complicates the management of persistency and data access across multiple services.
Innovation Solution
Assigning separate database schemas to each service and using table links to enable cross-schema access, allowing services to integrate on the database level while maintaining independence and avoiding name collisions, and employing a database schema management service to orchestrate deployments and schema management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate database schemas are assigned to each micro-service, then name collisions are avoided and service independence is maintained, but deployment dependencies and integration complexity increase
Solution Approach 1:
The patent divides the database into separate schemas for each micro-service, allowing each service to have its own isolated namespace. This segmentation prevents name collisions between services while maintaining clear boundaries. The database schema management service further segments the deployment process by orchestrating schema creation and table link establishment independently for each service.
Solution Approach 2:
The database schema management service acts as an intermediary between micro-services and the database. It receives deployment requests, creates appropriate schemas, manages table links between schemas, and coordinates dependencies. This intermediary layer abstracts the complexity of cross-schema access from individual services while maintaining their independence.
2Adaptability or versatility
If micro-services use different runtimes and database schemas, then technology flexibility is improved, but integration and data access management become more difficult
Solution Approach 1:
The database schema management service provides universal functionality for managing all micro-service database interactions. It handles schema creation, table link management, and dependency orchestration across different services regardless of their runtime or technology stack. This multi-functional approach simplifies data access management while allowing services to use diverse technologies.
Solution Approach 2:
The schema management service mediates between services with different runtimes and database schemas. It translates service-level data access requirements into database-level operations across schemas, managing table links and dependencies. This intermediary layer shields services from the complexity of cross-schema access while enabling flexible technology choices.
3Adaptability or versatility
If table links are used for cross-schema access, then services can integrate on database level while maintaining independence, but deployment orchestration complexity increases
Solution Approach 1:
The database schema management service performs preliminary actions by creating schemas and table links before micro-services are deployed. It pre-establishes the database structure and cross-schema relationships, so services can integrate seamlessly without dealing with deployment-time complexity. Dependencies are resolved in advance through orchestration of schema creation and table link establishment.
Data Source
AI summary
A first component originally has a persistency decoupled from a persistency of a second component. The second component requires a table from the persistency of the first component. The first component is assigned a first database schema and the second component is assigned a second database schema. A table link is created in the second database schema of the second component, wherein the table link refers to the required table from the first database schema of the first component.