Public Data Storage in Content Management Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing public data across multiple computer systems is computationally intensive and challenging due to the need to handle data accessibility rights and distribute data across various landscapes and content management systems.
Innovation Solution
Storing public data in a dedicated public content management system on a specific landscape, while keeping private data on local content management systems, allows for efficient data retrieval and management by separating computational loads and access rights.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If public data is distributed across multiple content management systems on different landscapes, then data accessibility and sharing between systems is improved, but computational complexity and management difficulty increase
Solution Approach 1:
A dedicated public content management system is introduced as an intermediary between multiple backend applications and the public data repository. This mediator handles all requests for public data, centralizing management responsibilities while allowing backend applications to access public data without direct complexity. The public CMS acts as a buffer that simplifies the interaction model between diverse systems and shared data.
Solution Approach 2:
The system segregates data management into distinct segments: private data remains in local content management systems while public data is isolated in a dedicated public CMS. This segmentation allows each segment to be managed independently with appropriate access controls and computational resources, reducing overall system complexity while maintaining accessibility.
2Productivity
If public data is stored in a dedicated public content management system, then computational loading on individual landscapes is reduced, but data retrieval complexity across landscapes increases
Solution Approach 1:
Multiple landscape systems are merged into a federated architecture where the public CMS serves as a common repository accessible by all landscapes. This combining approach allows computational work to be consolidated in the public CMS while maintaining distributed access, improving overall efficiency without creating a single point of failure.
Solution Approach 2:
The system adds a new dimensional layer to data access by introducing landscape-agnostic public data access alongside traditional landscape-specific private data access. This creates a two-dimensional access model where data can be retrieved either within the same landscape or from the public CMS across landscapes, providing flexibility without increasing fundamental complexity.
3Reliability
If private data is kept on local content management systems and public data is separated, then data security and access control are improved, but system architecture complexity increases
Solution Approach 1:
Different data types are assigned different storage locations based on their access requirements: private data remains in local content management systems with restricted access, while public data is placed in the dedicated public CMS with broader access. This local quality approach ensures each data type is stored where it provides maximum security and accessibility, with the architecture complexity justified by the security benefits.
Data Source
AI summary
Embodiments of the present disclosure include techniques for storing and retrieving public data. In one embodiment, data for backend applications running on different landscapes are stored in an associated content management system. A landscape of a plurality of landscapes includes a public content management system. Data designated at public may be stored by content management systems residing on different landscapes in the public content management system. Requests for public data are routed by local content managements systems to the public content management system, which then responds with the public data requested.