Cloud Service Attachment to Big Data Services

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud services face latency and bandwidth limitations when transferring large amounts of loosely structured data between cloud services and big data services due to geographical distances, which affects performance.

Innovation Solution

A system that includes a service locator to identify data services with data locality constraints, a dependency manager to determine if the capability data meets the deployment criteria of a cloud service, and an attachment controller to bind the cloud service to the data service based on proximity, ensuring deployment within the data locality constraint.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If cloud service and big data service are deployed at separate locations, then service independence and deployment flexibility are improved, but data transfer latency and bandwidth limitations worsen

Engineering Contradiction:
Improvedeployment flexibilityVSAvoiddata transfer latency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary identification of data services with locality constraints and evaluates their capability data before deployment. The dependency manager pre-assesses whether cloud services can be bound to specific data services based on deployment criteria, and the attachment controller pre-establishes bindings before actual data transfer operations begin, ensuring optimal location selection in advance to minimize subsequent latency

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements location-specific deployment by binding cloud services to data services based on geographical proximity requirements. The service locator identifies data services with data locality constraints, and the attachment controller binds cloud services to specific locations where data services are deployed, ensuring that each cloud service is deployed at the appropriate local location to minimize data transfer latency while maintaining deployment flexibility

Inventive Principle:
Principle #3Local quality

2Adaptability or versatility

If data is transferred over long geographical distances, then service deployment flexibility is improved, but bandwidth limitations and transfer performance worsen

Engineering Contradiction:
Improveservice deployment flexibilityVSAvoiddata transfer efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system performs preliminary evaluation of data service capability data including storage capacity, processor capacity, and connection configuration before binding cloud services. This advance assessment ensures that cloud services are bound to data services with sufficient capacity and optimal location, preventing future bandwidth bottlenecks while maintaining deployment flexibility

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system binds cloud services to specific data service locations based on evaluated capability data and deployment criteria. By selecting local data service instances with adequate capacity and optimal geographical location, the system maximizes data transfer efficiency for each specific deployment scenario while preserving overall service deployment flexibility

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10129330B2Attachment of cloud services to big data services
Publication Date: 2018.11.13 KYNDRYL INC
  • US10129330B2 patent drawing
  • US10129330B2 patent drawing
  • US10129330B2 patent drawing

AI summary

Methods and systems may provide for identifying a data service having a data locality constraint, determine whether capability data associated with the data service satisfies one or more deployment criteria of a cloud service and bind, if the capability data satisfies the one or more deployment criteria, the cloud service to the data service in accordance with the data locality constraint. In one example, the data service is identified based at least in part on a capability of the cloud service to be provisioned with a deployment location that complies with the data locality constraint.