Open service broker compliant service broker using serverless functions
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.
1 . A system associated with an Open Service Broker (“OSB”) Application Programming Interface (“API”) computing environment, comprising:
a serverless runtime to receive an OSB request trigger from an API gateway;
database storage that contains orchestration sagas;
a serverless deployment mechanism, including:
a computer processor, and
computer memory, coupled to the computer processor, storing instructions that, when executed by the computer processor cause the processor to:
(i) responsive to the OSB request trigger, arrange for compute resources to handle the OSB request trigger be provisioned on-demand, and
(ii) instantiate a plurality of serverless functions with OSB service bindings, each executing in a resource-constrained container, wherein the plurality of serverless functions span multiple API domains and access the database storage;
a finite state machine orchestrator to orchestrate, using semantics, a sequence of activities for the sagas by the plurality of serverless functions; and
a service instance to respond to chained calls from the plurality of serverless functions in accordance with the sequence of activities.
2 . The system of claim 1 , wherein the OSB API computing environment is associated with at least one of: (i) a cloud infrastructure provider, and (ii) an on-premises deployment.
3 . The system of claim 1 , wherein the OSB request trigger comprises a stateless Hyper-Text Transfer Protocol (“HTTP”) trigger.
4 . The system of claim 3 , wherein the OSB API comprises a Representational State Transfer (“REST”) API.
5 . The system of claim 1 , wherein a service broker API defines a domain specific function handler responsible for resource-oriented operations.
6 . The system of claim 1 , wherein the API gateway serves as a single entry-point for all Hyper-Text Transfer Protocol (“HTTP”) request handlers for a service broker.
7 . The system of claim 6 , wherein the API gateway proxies route service broker endpoint requests through an event sourcing mechanism.
8 . The system of claim 6 , wherein a service broker handler is instantiated and loaded on demand to provide dynamic function invocation.
9 . The system of claim 1 , wherein asynchronous lifecycle operations are supported service instances.
10 . A computer-implemented method associated with an Open Service Broker (“OSB”) Application Programming Interface (“API”) computing environment, comprising:
receiving, at a serverless runtime from an API gateway, an OSB request trigger;
responsive to the OSB request trigger, arranging by a serverless deployment mechanism for compute resources to handle the OSB request trigger be provisioned on-demand;
defining, by a service broker API, a domain specific function handler responsible for resource-oriented operations, wherein the handler is instantiated and loaded on demand to provide dynamic function invocation;
instantiating a plurality of serverless functions with OSB service bindings, each executing in a resource-constrained container, wherein the plurality of serverless functions span multiple API domains;
accessing database storage that contains orchestration sagas;
orchestrating, by a finite state machine, a sequence of activities for the sagas using semantics; and
responding, by a service instance, to chained calls from the plurality of serverless functions in accordance with the sequence of activities.
11 . The method of claim 10 , wherein the OSB API computing environment is associated with at least one of: (i) a cloud infrastructure provider, and (ii) an on-premises deployment.
12 . The method of claim 10 , wherein the OSB request trigger comprises a stateless Hyper-Text Transfer Protocol (“HTTP”) trigger.
13 . The method of claim 12 , wherein the OSB API comprises a Representational State Transfer (“REST”) API.
14 . The method of claim 10 , wherein the API gateway serves as a single entry-point for all Hyper-Text Transfer Protocol (“HTTP”) request handlers for a service broker.
15 . The method of claim 14 , wherein the API gateway proxies route service broker endpoint requests through an event sourcing mechanism.
16 . A non-transitory, computer readable medium having executable instructions stored therein that, when executed by a computer processor cause the processor to perform a method associated with an Open Service Broker (“OSB”) Application Programming Interface (“API”) computing environment, the method comprising:
receiving, at a serverless runtime from an API gateway, an OSB request trigger;
responsive to the OSB request trigger, arranging by a serverless deployment mechanism for compute resources to handle the OSB request trigger be provisioned on-demand;
instantiating a plurality of serverless functions with OSB service bindings, each executing in a resource-constrained container, wherein the plurality of serverless functions span multiple API domains;
accessing database storage that contains orchestration sagas;
orchestrating, by a finite state machine, a sequence of activities for the sagas using semantics; and
responding, by a service instance, to chained calls from the plurality of serverless functions in accordance with the sequence of activities.
17 . The medium of claim 16 , wherein the OSB API computing environment is associated with at least one of: (i) a cloud infrastructure provider, and (ii) an on-premises deployment.
18 . The medium of claim 16 , wherein the API gateway serves as a single entry-point for all Hyper-Text Transfer Protocol (“HTTP”) request handlers for a service broker.
19 . The medium of claim 18 , wherein the API gateway proxies route service broker endpoint requests through an event sourcing mechanism and a service broker handler is instantiated and loaded on demand to provide dynamic function invocation.
20 . The medium of claim 17 , wherein the OSB request trigger comprises a stateless Hyper-Text Transfer Protocol (“HTTP”) trigger the OSB API comprises a Representational State Transfer (“REST”) API.