Serverless Service Broker for On-Demand OSB Provisioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Creating and maintaining applications across various platforms and multi-cloud computing environments is challenging for independent software vendors, and existing server-oriented service brokers incur high infrastructure costs and inefficiencies.
Innovation Solution
Implementing a serverless deployment model for service brokers using serverless functions, which provision compute resources on-demand and enable domain-oriented development, reducing costs and improving efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a server-oriented service broker is used to manage service lifecycles across multi-cloud environments, then service provisioning and management capabilities are improved, but infrastructure costs and resource utilization efficiency deteriorate
Solution Approach 1:
The service broker is implemented as serverless functions that automatically provision and manage service instances without requiring persistent server infrastructure. The system self-adjusts resource allocation based on actual service requests, eliminating the need for continuously running servers and reducing infrastructure costs while maintaining multi-cloud service management capabilities
Solution Approach 2:
The patent transitions from a traditional server-based architecture to a serverless architecture, fundamentally changing the operational parameters of the service broker. This parameter change enables on-demand resource provisioning, where compute resources are allocated only when services need to be provisioned or managed, thereby reducing idle resource consumption and infrastructure costs
2Reliability
If traditional server-based service brokers are deployed to handle service lifecycle commands, then service management functionality is improved, but resource utilization efficiency and development productivity deteriorate
Solution Approach 1:
The service broker functionality is segmented into discrete serverless functions that can be independently developed, deployed, and executed. Each function handles specific service lifecycle commands (provision, connect, disconnect, deprovision), allowing developers to work on individual functions in isolation and improving overall development productivity while maintaining reliable service management through the collective functionality of all segments
3Loss of energy
If serverless functions are used to implement service broker, then resource utilization efficiency is improved, but system complexity in managing service bindings deteriorates
Solution Approach 1:
The patent introduces service bindings as intermediary objects that manage the relationships between serverless functions and service instances. These bindings act as mediators that automatically handle the complexity of resource allocation, authentication, and service instance management, allowing the serverless functions to focus on core service logic while the bindings manage the intricate details of resource coordination
Data Source
AI summary
Methods and systems may be associated with an Open Service Broker (“OSB”) Application Programming Interface (“API”) computing environment. A serverless runtime may receive an OSB request trigger from an API gateway. A serverless deployment mechanism may, responsive to the OSB request trigger, arrange for compute resources to handle the OSB request trigger be provisioned on-demand. The system may then instantiate an instance of a serverless function with OSB service bindings. The OSB API computing environment might, for example, be associated with a cloud infrastructure provider or an on-premises deployment. Such an approach may provide for on-demand execution, better resource constraints, and/or domain-oriented development.