Collaboration Attribute Partitioning for Cloud Content Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cloud-based shared content management platforms face performance limitations in accessing shared content due to centralized collaboration attributes, leading to increased latency as the number of collaborators grows, as they often require accessing geographically distant centralized attribute tables.
Innovation Solution
Implementing collaboration attribute partitioning, where outgoing and incoming collaboration attributes are generated and stored on partitions close to the users, allowing for low-latency access by partitioning collaboration attributes to match user locations, thereby improving access performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If collaboration attributes are centralized in one database table and location, then data consistency and management simplicity are improved, but access latency increases especially when users are geographically distant from the centralized location
Solution Approach 1:
The patent segments the centralized collaboration attributes table into multiple distributed shards across different geographic locations. Each shard stores a portion of the collaboration attributes, allowing users to access attributes from the nearest shard rather than a single centralized location. This segmentation reduces access latency while maintaining data consistency through coordinated shard management.
Solution Approach 2:
The patent implements local quality by placing collaboration attribute shards geographically close to the users who need to access them. Instead of uniform centralized storage, the system creates locally-optimized attribute storage locations that reduce the physical and network distance between users and their required collaboration attributes, thereby improving access performance.
2Loss of time
If content is partitioned and co-located near users to improve access performance, then access latency is reduced, but collaboration attribute access becomes problematic when attributes remain centralized
Solution Approach 1:
The patent merges the partitioning strategy for content with the partitioning strategy for collaboration attributes. Both content and collaboration attributes are partitioned using the same sharding mechanism and stored in co-located shards. This merging simplifies the overall system architecture by using a unified partitioning approach rather than separate mechanisms for content and attributes.
3Adaptability or versatility
If the number of collaborators increases, then collaboration capability and versatility are improved, but access latency increases due to centralized attribute table queries
Solution Approach 1:
The patent segments the collaboration attribute access load across multiple distributed shards rather than concentrating all attribute queries on a single centralized table. As the number of collaborators increases, the segmented shard architecture distributes the query load, preventing any single server from becoming a bottleneck and maintaining access latency performance even with large numbers of collaborators.
Data Source
AI summary
Systems for managing shared content in a cloud-based service platform. A method commences upon identifying one or more storage devices that store one or more content objects. The storage devices may be partitioned into geographically distant locations. A first partition in one geography is associated with a first set of content objects and a second partition is associated with a second set of content objects. An inviter-collaborator generates a set of outgoing collaboration attributes pertaining to a shared content object from the first partition. The outgoing collaboration attributes are stored on the inviter's partition. An invitee-collaborator accepts the invitation and generates a set of incoming collaboration attributes that derive from the set of outgoing collaboration attributes. The set of incoming collaboration attributes are stored on the invitee's partition. The invitations can be sent and received through operation of a web application that facilitates offering invitations and acceptance of those invitations.