Cloud Content Management System Distributed Peer Architecture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud-based Content Management Systems (CMSs) face bottlenecks and long transaction times due to the client-server model, which becomes inefficient when handling multiple requests simultaneously.

Innovation Solution

Distributing content management services across multiple servers in a Cloud computing environment, allowing for dynamic replication of the content management application based on resource analysis and predetermined rules to maintain high throughput, leveraging peer-to-peer communication and local storage for faster data retrieval.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a client-server model is used for content management, then centralized control and data management are achieved, but bottlenecks and long transaction times occur when multiple requests are received simultaneously

Engineering Contradiction:
Improvecentralized controlVSAvoidtransaction throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the centralized content management system into multiple distributed peer servers. Each peer server can independently handle content management requests, dividing the workload across multiple nodes. This segmentation eliminates the single-point bottleneck of the traditional client-server model while maintaining centralized control through distributed consensus mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transitions from a two-dimensional client-server architecture to a multi-dimensional peer-to-peer network architecture. By adding the dimension of distributed peer nodes, the system can handle requests from multiple directions simultaneously, increasing throughput while maintaining control through the overlay network structure.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Productivity

If content management services are distributed across multiple servers, then transaction times and bottlenecks are reduced, but system complexity increases

Engineering Contradiction:
Improvetransaction throughputVSAvoidsystem architecture
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Each peer server in the distributed system performs multiple functions: content storage, request handling, data replication, and consensus participation. This multi-functionality reduces the need for specialized components and simplifies the overall system architecture despite the distributed nature, as each node is a self-sufficient universal unit.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The distributed peer servers autonomously manage their own operations including local content storage, request processing, and participation in consensus algorithms. This self-service capability reduces the need for centralized coordination overhead, simplifying the system architecture while maintaining high throughput through independent node operations.

Inventive Principle:
Principle #25Self-service

3Speed

If content is stored locally on workstations, then data retrieval speed is improved, but data consistency and control become more difficult to maintain

Engineering Contradiction:
Improvedata retrieval speedVSAvoiddata consistency
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system implements feedback mechanisms where peer servers continuously exchange data consistency information and synchronization status. This feedback loop enables local workstations to maintain up-to-date content while preserving fast local access, as the distributed consensus protocol ensures all peers have consistent views of the content state.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Content is pre-replicated to local workstations before requests are made, enabling fast local retrieval. The preliminary action of distributing content copies to multiple peers ensures that when retrieval is needed, the data is already available locally, while consistency is maintained through subsequent synchronization protocols.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10257109B2Cloud-based content management system
Publication Date: 2019.04.09 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10257109B2 patent drawing
  • US10257109B2 patent drawing
  • US10257109B2 patent drawing

AI summary

Methods and apparatus, including computer program products, implementing and using techniques for providing content management services in a Cloud computing environment. A content management application and associated content is distributed across a set of servers in a Cloud computing environment. Requests for Cloud content management services are received from requesters that are using the Cloud computing environment. The received requests are analyzed to determine an amount of resources needed for responding to the requests. Based on the results of the analysis and a predetermined set of rules, the content management application is dynamically replicated to additional servers within the Cloud computing environment. Any instance of the content management application is capable of replying to any received request so as to maintain a high throughput of the Cloud content management services.