System and method for a unified interface to networked webservices
Abstract
A system and method for a function-as-a-service platform that includes creating a set of distinct webservices within a webservice hosting platform, which involves receiving a webservice resource definition, processing the webservice resource definition, and instantiating a webservice of the webservice resource definition within the webservice hosting platform; and invoking a webservice instantiated in the webservice hosting platform for a client device, which involves: receiving a webservice function call request, executing the webservice function call request on a webservice instance, and responding to the webservice function call request with a result of the webservice.
Claims
exact text as granted — not AI-modifiedWe claim:
1 . A method comprising:
creating a set of distinct webservices within a webservice hosting platform, the set of webservices created by a set of distinct accounts, and the creation of a webservice comprising:
receiving a webservice resource definition,
processing the webservice resource definition, and
instantiating a webservice of the webservice resource definition within the webservice hosting platform; and
invoking of a webservice instantiated in the webservice hosting platform for a client device, wherein responsive to an invocation is a process comprising:
receiving a webservice function call request,
executing the webservice function call request on a webservice instance, and
responding to the webservice function call request with a result of the webservice.
2 . The method of claim 1 , further comprising providing a set of function call interfaces that comprise at least a command line interface and a library interface; and wherein the webservice function call request is received through at least one of the set of function call interfaces.
3 . The method of claim 1 , further comprising providing a set of function call interfaces that comprises at least a command line interface; and wherein the webservice function call request is received through at least one of the set of function call interfaces.
4 . The method of claim 3 , further comprising providing manual documentation through the command line interface to the set of webservices of the webservice hosting platform.
5 . The method of claim 1 , further comprising providing a query interface to the set of webservices, which comprises generating a set of webserver query results in response to a webservice query.
6 . The method of claim 5 , wherein the webservice function call is made in the form of a webservice query; and further comprising automatically selecting one of the set of webservice query results as the invoked webservice used in executing the function call.
7 . The method of claim 6 , wherein selecting one of the set of webservice query results selects the invoked webservice at least partially based on webservice popularity ranking.
8 . The method of claim 1 , further comprising tracking usage of the webservices.
9 . The method of claim 8 , further comprising proactively scaling webservice instances of at least one webservice in response to usage of the webservice.
10 . The method of claim 8 , further comprising architecting deployment of a set of webservices used in combination in response to tracked usage of the webservices.
11 . The method of claim 8 , wherein the webservice resource definition comprises usage billing configuration; wherein tracking usage of the webservice comprises tracking usage by a second account; and further comprising generating a billing report according to usage of the second account and the usage billing configuration.
12 . The method of claim 1 , further comprising analyzing combined usage of a first webservice and a second webservice; and architecting deployment of the first and second webservices based on the combined usage of the first webservice and the second webservice.
13 . The method of claim 12 , wherein combined usage is determined by temporal proximity of invocation by an account instance.
14 . The method of claim 12 , wherein combined usage is determined through detecting usage of at least a second webservice by a first webservice; and wherein architecting deployment can comprise automatically instantiating an instance of the second webservice in coordination with instantiation of an instance of the first webservice.
15 . The method of claim 14 , wherein instantiating an instance of the second webservice in coordination with instantiation of an instance of the first webservice comprises colocating instances of the first and second webservice.
16 . The method of claim 1 , further comprising caching a response to a function call and returning the cached response to second corresponding function call.
17 . The method of claim 1 , further comprising providing a generic interface to a set of webservices; and when the webservice function call request is to the generic interface, dynamically selecting one of a set of compatible webservices for use in executing the function call.
18 . The method of claim 1 , wherein the webservice resource definition includes a function definition and configuration definition.
19 . The method of claim 18 , wherein configuration definition can include namespace configuration, permissions, usage limits, and documentation.
20 . A system for a function-as-a-service platform comprising:
a webservice management system configured to:
receive a webservice resource definition,
process the webservice resource definition, and
instantiate a webservice of the webservice resource definition within the function-as-a-service platform;
a platform interface gateway configured to:
receive a webservice function call request,
execute the webservice function call request on a webservice instance, and
respond to the webservice function call request with a result of the webservice; and
an infrastructure management system configured to scale webservice instances based in part on usage of webservices through the platform interface gateway.Join the waitlist — get patent alerts
Track US2020389529A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.