Proxy Service Broker for Partner Cloud Service Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud-computing Platform as a Service (PaaS) systems, seamless integration of Hoster- and Partner-provided services is challenging, leading to issues like network latency, limited service availability, data security concerns, and increased total cost of ownership due to the need for single dedicated service users and shared throttling rules.
Innovation Solution
Implementing a Proxy Service Broker on the Hoster PaaS to manage requests for Partner PaaS services, allowing users to access Partner services without direct interaction with the Partner's platform, by creating instances and binding services in a way that each service consumer has a dedicated instance, reducing the need for shared credentials and throttling rules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a single dedicated service user is used to access Partner PaaS services, then service access is simplified, but network latency increases and throughput decreases
Solution Approach 1:
The patent segments the service access model by creating separate service instances for each consumer instead of using a single shared service user. Each consumer gets their own instance, which eliminates the need for request routing through a single user and reduces network latency while maintaining operational simplicity through automated instance management.
2Quantity of substance
If multiple consumers share a single service instance, then resource utilization increases, but data security is compromised
Solution Approach 1:
The patent implements segmentation by creating separate service instances for each consumer, ensuring that data uploaded by one consumer remains isolated and secure. This maintains resource efficiency while eliminating the security risks associated with shared service instances.
Solution Approach 2:
The service broker acts as an intermediary that automatically manages the creation, binding, and allocation of separate service instances to each consumer. This intermediary layer enables secure isolated instances while maintaining high resource utilization through automated instance management.
3Device complexity
If a single dedicated service user is used, then service provisioning is simplified, but service availability is reduced due to locking issues
Solution Approach 1:
The patent segments the service user into multiple separate service instances, one for each consumer. This eliminates service locking issues that occur when multiple consumers share a single user account, thereby improving service availability while the service broker maintains simplified provisioning through automated instance creation.
4Device complexity
If shared throttling rules are applied to a dedicated service user, then rule management is simplified, but productivity is reduced due to shared rate limits
Solution Approach 1:
The patent segments throttling control by creating separate service instances for each consumer, allowing each to have their own rate limits and throttling rules. This eliminates the bottleneck of shared throttling rules while the service broker maintains simplified rule management through automated provisioning and configuration.
Data Source
AI summary
A Proxy Service Broker on a Hoster Platform as a Service (PaaS) receives a request for a Service Catalog including PaaS services available from a Partner PaaS. Using the Proxy Service Broker, creation of an instance of a Partner PaaS service selected from the Service Catalog is initiated. Using the Proxy Service Broker, a call is transmitted to a Partner Service Broker on the Partner PaaS to create the instance of the Partner PaaS service executing on the Partner PaaS. An Application is deployed on the Hoster PaaS to consume the instance of the Partner PaaS service. The deployed Application is bound with the instance of the Partner PaaS service and directly consumes the bound Partner PaaS service.