Function as a service console for an online application exchange platform

A method for managing an application exchange platform includes receiving, from a developer, a service function, wherein the service function includes configuration details for an application available through an online application exchange. The method includes deploying the service function in the application exchange, identifying a first domain event requesting access to the service function from a user, and calling the service function in the online application exchange, in response to the first domain event. The method also includes recording a metric associate with the service function and a return parameter, emitting a second domain event indicative of a completion of the service function, and charging, with a billing tool, an appropriate party based on a usage metadata for the service function. A system and a non-transitory, computer-readable memory storing instructions to cause the system to perform the above method are also provided.

BACKGROUND

Field

The present disclosure relates to online platforms for developers to offer applications for the public and keep track of domain events associated with one or more applications in a flexible manner. More specifically, the present disclosure provides function as a service (FaaS) handles in an online application exchange platform to allow developers to deploy code for added value to an application when triggered by a domain event, and keep track of the service costs.

Related Art

Current application exchange platforms have rigid architectures that preclude the tracking of added features to one or more applications, especially in terms of service costs. Typically, the usage of computational resources and access to authorized parties creates a complex track that results in revision overtime and ultimately loss revenue. When a user wants to expand access to an application service or perform outgoing calls to a third party, there is no simple way to handle subscriptions and credentials, keep track of billing items, and assess what party is responsible for what piece of the incurred cost. What is needed is a flexible way to manage an application exchange platform that provides developers, platform owners, and application end users direct access to added features, new applications, new services, and a transparent cost distribution.

In the figures, elements and steps denoted by the same or similar reference numerals are associated with the same or similar elements and steps, unless indicated otherwise.

SUMMARY

In a first embodiment, a computer-implemented method includes receiving, from a developer, a service function, wherein the service function includes configuration details for an application available through an online application exchange. The computer-implemented method also includes deploying the service function in the online application exchange, identifying a first domain event requesting access to the service function from a user, and calling, with a wrapper function, the service function in the online application exchange, in response to the first domain event. The computer-implemented method also includes recording, with a wrapper function executed on top of the service function, a metric associated with the service function and a return parameter, emitting a second domain event indicative of a completion of the service function, and charging, with a billing tool, an appropriate party based on a usage metadata for the service function.

In a second embodiment, a system includes a memory, storing instructions and one or more processors. The one or more processors are configured to execute the instructions to cause the system to receive, from a developer, a service function, wherein the service function includes configuration details for an application available through an online application exchange. The one or more processors also execute instructions to cause the system to deploy the service function in the online application exchange, to identify a first domain event requesting access to the service function from a user, to call, with a wrapper function, the service function in the online application exchange, in response to the first domain event, and to record, with a wrapper function executed on top of the service function, a metric associated with the service function and a return parameter. The one or more processors also execute instructions to cause the system to emit a second domain event indicative of a completion of the service function, to charge, with a billing tool, an appropriate party based on a usage metadata for the service function, and to grant fine grained permissions to an end user based on the configuration details.

In a third embodiment, a non-transitory, computer-readable medium stores instructions which, when executed by a processor, cause a computer to perform a method, the method includes receiving, from a developer, a service function, wherein the service function includes configuration details for an application available through an online application exchange, deploying the service function in the online application exchange, and identifying a first domain event requesting access to the service function from a user. The method also includes calling, with a wrapper function, the service function in the online application exchange, in response to the first domain event, recording, with a wrapper function executed on top of the service function, a metric associated with the service function and a return parameter, and emitting a second domain event indicative of a completion of the service function. The method also includes charging, with a billing tool, an appropriate party based on a usage metadata for the service function, granting fine grained permissions to an end user based on the configuration details, and decrypting a secret key in the configuration details upon receipt of the first domain event.

In yet another embodiment, a system includes a means for storing instructions and a means for executing the instructions. The means for executing instructions are configured to cause the system to receive, from a developer, a service function, wherein the service function includes configuration details for an application available through an online application exchange. The means for executing instructions also causes the system to deploy the service function in the online application exchange, to identify a first domain event requesting access to the service function from a user, to call, with a wrapper function, the service function in the online application exchange, in response to the first domain event, and to record, with a wrapper function executed on top of the service function, a metric associated with the service function and a return parameter. The means for executing instructions also causes the system to emit a second domain event indicative of a completion of the service function, to charge, with a billing tool, an appropriate party based on a usage metadata for the service function, and to grant fine grained permissions to an end user based on the configuration details.

DETAILED DESCRIPTION OF THE FIGURES

Current application exchange platforms have rigid architectures that preclude the tracking of added features to one or more applications, especially in terms of service costs. Typically, the usage of computational resources and access to authorized parties creates a complex track that results in revision overtime and ultimately loss revenue for developers and platform owners. Ultimately, these deficiencies are passed down to the end users (e.g., application subscribers) in the form of cumbersome interactions and unsatisfactory performance.

To resolve the above technical problems arising in the field of computer networking, an application exchange platform as disclosed herein offers a user interface (UI) where a developer can select which domain event they wish to subscribe to. In some embodiments, a developer may also specify configurations such as whitelisted universal resource locations (URLs) that a function in an application may call out to. The developer may also establish fine grained permissions or roles to grant a function in the application, as well as an authorization context such as secrets, and external authorization server URLs.

In addition, some embodiments include an authorization server to offer a developer the ability to implement authentication of external resources to make external calls to whitelisted URLs. In another embodiment, the platform includes an interceptor to inject authorization credentials to whitelisted URLs into function calls configured by the developer.

To facilitate the handling of service functions in an application, an application exchange platform as disclosed herein may provide a lightweight, wrapper function. The wrapper function measures the metrics of tool usage while the application is run by an end user. Based on this metric data, once the service function completes execution, the metrics can be forwarded to a usage/billing service and charged to the appropriate party. In some embodiments, a developer may wish to absorb the cost themselves, and in some embodiments, the developer may want to transfer the fees onto the end user. The fees generated can be determined by the exchange platform, and the extra revenue could be split between the developer, the exchange platform, and the marketplace owner. This could be decided by the developer in one embodiment, in another it might be decided by the exchange platform. The detailed cost information can be propagated by the Wrapper Function when it reports the function result/usage. The Wrapper Function can also report unhandled exceptions to the dashboard for the developer.

System Overview

FIG.1illustrates an example architecture10suitable to provide an online application exchange platform100, according to some embodiments. Online application exchange platform100may include one or more servers130-1and130-2(hereinafter, collectively referred to as “servers130”) coupled to a database152. Online application exchange platform100may be accessed by one or more developers using client devices110-1,110-2, through110-n(hereinafter, collectively referred to as “client devices110”). The developers may create and upload applications122-1,122-2, through122-n(hereinafter, collectively referred to as “applications122”) onto online application exchange platform100via a network150.

Servers130may include any device having an appropriate processor, memory, and communications capability for hosting the documents and applications associated with the device provisioning engine. The device provisioning engine may be accessible by multiple participants through various client devices110over the network150. Client devices110can be, for example, handsets, desktop computers (coupled with handsets, or standalone), mobile computers, tablet computers (e.g., including e-book readers), mobile devices (e.g., a smartphone or PDA), or any other devices having appropriate processor, memory, and communications capabilities for accessing the device provisioning engine on one of servers130. Network150can include, for example, any one or more of a local area network (LAN), a wide area network (WAN), the Internet, and the like. Further, network150can include, but is not limited to, any one or more of the following network topologies, including a bus network, a star network, a ring network, a mesh network, a star-bus network, tree or hierarchical network, and the like.

FIG.2is a block diagram200illustrating an example server130and client device110in the architecture10, according to certain aspects of the disclosure. Client device110and server130are communicatively coupled over network150via respective communications modules218-1and218-2(hereinafter, collectively referred to as “communications modules218”). Communications modules218are configured to interface with network150to send and receive information, such as data, requests, responses, and commands to other devices on the network. Communications modules218can be, for example, modems or Ethernet cards.

Client device110may be any one of a desktop computer, a laptop, or a mobile computing device. Client device110may include a processor212-1and a memory220-1. Processor212-1is configured to execute instructions, such as instructions physically coded into processor212-1, instructions received from software in memory220-1, or a combination of both. An input device214and an output device216enable the user to interact with client device110. Examples of input device214and output device216may include a mouse, a keyboard, a display, a touch-interactive display, and the like. A user of client device110may use input device214to submit a document or a media file to application programming interface (API) layer230via a user interface of application222. Application222may enable the user of client device110to edit a document (text editor), to create presentation slides, or a chart including data, or perform any other computational task hosted by server130.

Server130includes a memory220-2, a processor212-2, and communications module218-2. Memory220-2includes a subscription management engine232. Subscription management engine232includes instructions which, when executed by processor212-2, cause server130to perform at least partially steps as disclosed herein. In some embodiments, subscription management engine232includes instructions to communicate with application222to add a user or a group of users, or to add a resource address that the users of application222may call, while running. An API layer230handles the communications between server130and application222in client device110. Subscription management engine232may include an event management tool240, billing management tool242, an identity management tool244, an application discovery tool246, a developer tool248, and a wrapper function tool250.

Wrapper function250is configured to measure the metrics of tool usage while application222is running. Based on this metric data, subscription management engine232generates a usage/billing service. The detailed cost information can be propagated by wrapper function250when it reports the function result/usage. Wrapper function250can also report unhandled exceptions to the dashboard for the developer.

Furthermore, in some embodiments, subscription management engine232may include instructions to retrieve and provide to one or more users at least some of the data in a database252associated with a given application222. Hereinafter, processors212-1and212-2will be collectively referred to as “processors212,” and memories220-1and220-2will be collectively referred to as “memories220.”

The user may access application222installed in memory220-1of client device110. The user may access application222via a web browser installed in client device110. Execution of application222may be controlled by processor212-1in client device110. In some embodiments, application222is downloaded and installed by the user into client device110, from server130.

FIG.3illustrates a group of online applications322-1through322-24(hereinafter, collectively referred to as “applications322”) offered in an online application exchange platform300, according to some embodiments. Applications322may include desktop-based applications such as text editors, comma delimited documents, table management applications, presentation creating applications, document editors, design applications, and the like. In some embodiments, an end user may access and run applications322via a web browser. In some embodiments, an end user may have a plug in for applications322installed in a client device, and run the application directly from the plug in.

FIG.4illustrates a dashboard400for an application422in an application exchange platform, according to some embodiments. Dashboard400enables developers to view functions usages and their outcome. In dashboard400, an application422is selected by a developer of the application exchange platform. Dashboard400illustrates graphically, to the developer, different aspects of application performance associated with a service function, FaaS405, such as a subscription roster410and an event log415. Subscription roster410may include names, addresses, and contact information for the users that have access to application422and the resources it uses and provides (CPU, GPU, memory allocation, and the like). Subscription roster410may also include authorization credentials for the users, passwords and access codes, encrypted keys, and associated scripts that users may access or activate while logging into application422. Event log415may include a list of events and times of occurrence for application422. In some embodiments, event log415may include details as to the time a user has been logged into application422, and any external call for resources and other services. Accordingly, the developer may have a clear indication of the costs incurred by different users while logged into application422. In one embodiment it is possible for a function to be triggered by one or many events. The function can be written in a way that an abstract function can handle multiple types of events.

Dashboard400may also include graphical displays such as dials450-1,450-2, and450-3(hereinafter, collectively referred to as “dials450”), or other graphical indicators for different metrics (e.g., metric A, metric B, metric C, and the like), wherein the metrics may be indicative of CPU usage, GPU usage, or memory usage of a given user, while logging into application422.

Through event log415, the developer may select an event, and be directed to an in browser integrated development environment (IDE), or alternatively a repository they can push to (e.g., a Git. repository) that has an auto generated method entry point to provide an event object. The developer can call internal GraphQL or REST application programming interfaces, emit their own events, or run any code they wish. In some embodiments, dashboard400may provide a software development kit (SDK)420for easier integration of FaaS405into application422. Dashboard400may enable a developer to retry failed events, or cancel long running events that they would like to terminate.

In some embodiments, FaaS405may be configured to return parameters or an object with fields (e.g., dials450for metrics A, B, or C), as a result of an event or action. The values in dials450can represent the resulting status of the function, for example, an HTTP return code or pre-defined states of the function, such as SUCCEEDED, FAILED, and PENDING.

FIG.5is a flowchart illustrating steps in a method500for managing a service function in an application exchange platform, according to some embodiments. Method500may be performed at least partially by any one of the network servers hosting a subscription management engine (e.g., subscription management engine232), while communicating with any one of a plurality of client devices (e.g., servers130and clients110). To perform at least some of the steps in method500, the subscription management engine may access an event management tool, a billing management tool, an identity management tool, an application discovery tool, a developer tool, and a wrapper function as disclosed herein (e.g., event management tool240, billing management tool242, identity management tool244, application discovery tool246, developer tool248, and wrapper function250). At least some of the steps in method500may be performed by a computer having a processor executing commands stored in a memory of the computer (e.g., processors212and memories220). For example, at least some of the commands may be included in an application installed in a client device accessible by a user, and hosted via an API layer in the network server (e.g., application222, API layer230). Further, steps as disclosed in method500may include retrieving, editing, and/or storing files in a database that is part of, or is communicably coupled to, the computer (e.g., database252). Methods consistent with the present disclosure may include at least some, but not all, of the steps illustrated in method500, performed in a different sequence. Furthermore, methods consistent with the present disclosure may include at least two or more steps as in method500performed overlapping in time, or almost simultaneously.

Step502includes receiving, from a developer, a service function, wherein the service function includes configuration details for an application available through an online application exchange. In some embodiments, the configuration details include a whitelist and an external authentication network address, and step502includes granting fine grained permissions to end users based on the configuration details. In some embodiments, the configuration details include a secret key, and step502includes decrypting the secret key upon receipt of the first domain event.

Step504includes deploying the service function in the online application exchange. In some embodiments, the first domain event is a subscription request to an application from a user, and step504includes requesting user credentials to validate a user account for the application.

Step506includes identifying a first domain event requesting access to the service function from a user.

Step508includes calling, with a wrapper function, the service function in the online application exchange, in response to the first domain event.

Step510includes recording, with a wrapper function executed on top of the service function, a metric associated with the service function and a return parameter. In some embodiments, step510includes reporting, to the developer, the metric associated with the service function. In some embodiments, step510includes recording a return parameter provided by the service function. In some embodiments, step510includes generating a value for the metric as a nonlinear combination of a CPU usage, a number of threads used by the service function, and a memory usage. In some embodiments, the return parameter includes one of a “success,” “fail,” or “pending” event, and step510includes resubmitting a request for the service function when the return parameter is failed.

Step512includes emitting a second domain event indicative of a completion of the service function.

Step514includes charging, with a billing tool, an appropriate party based on a usage metadata for the service function. In some embodiments, step514includes determining a cost that has a non-linear dependence with a computational time usage to execute the service function. In some embodiments, step514includes updating a function dashboard in a developer console when the second domain event is emitted. In some embodiments, step514includes recording the domain event indicative of a completion of the service function in a database. In some embodiments, step514includes charging either of an end user of the application or a platform owner, based on a selection by the developer.

FIG.6is a flowchart illustrating steps in a method600for configuring a wrapper function, according to some embodiments. Method600may be performed at least partially by any one of the network servers hosting a subscription management engine (e.g., subscription management engine232), while communicating with any one of a plurality of client devices (e.g., servers130and clients110). To perform at least some of the steps in method600, the subscription management engine may access an event management tool, a billing management tool, an identity management tool, an application discovery tool, a developer tool, and a wrapper function as disclosed herein (e.g., event management tool240, billing management tool242, identity management tool244, application discovery tool246, developer tool248, and wrapper function250). At least some of the steps in method600may be performed by a computer having a processor executing commands stored in a memory of the computer (e.g., processors212and memories220). For example, at least some of the commands may be included in an application installed in a client device accessible by a user, and hosted via an API layer in the network server (e.g., application222, API layer230). Further, steps as disclosed in method600may include retrieving, editing, and/or storing files in a database that is part of, or is communicably coupled to, the computer (e.g., database252). Methods consistent with the present disclosure may include at least some, but not all, of the steps illustrated in method600, performed in a different sequence. Furthermore, methods consistent with the present disclosure may include at least two or more steps as in method600performed overlapping in time, or almost simultaneously.

Step602includes receiving, from a service function executed by an application, a value for the usage of a computational resource when the service function has completed a task.

Step604includes generating a metric indicator with the value for the usage of the computational resource.

Step606includes determining a cost incurred by a third party based on the metric indicator.

Step608includes preparing and distributing an invoice for the cost incurred by the third party to a designated party.

Hardware Overview

FIG.7is a block diagram illustrating an example computer system700with which the client devices110and servers130ofFIGS.1and2, and methods500and600can be implemented, according to some embodiments. In certain aspects, computer system700may be implemented using hardware or a combination of software and hardware, either in a dedicated server, or integrated into another entity, or distributed across multiple entities.

Computer system700(e.g., client device110and server130) includes a bus708or other communication mechanism for communicating information, and a processor702(e.g., processors212) coupled with bus708for processing information. By way of example, the computer system700may be implemented with one or more processors702. Processor702may be a general-purpose microprocessor, a microcontroller, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a state machine, gated logic, discrete hardware components, or any other suitable entity that can perform calculations or other manipulations of information.

Computer system700can include, in addition to hardware, a code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them stored in an included memory704(e.g., memories220), such as a Random Access Memory (RAM), a flash memory, a Read-Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable PROM (EPROM), registers, a hard disk, a removable disk, a CD-ROM, a DVD, or any other suitable storage device, coupled to bus708for storing information and instructions to be executed by processor702. The processor702and the memory704can be supplemented by, or incorporated in, a special purpose logic circuitry.

Computer system700further includes a data storage device706such as a magnetic disk or optical disk, coupled to bus708for storing information and instructions. Computer system700may be coupled via input/output module710to various devices. Input/output module710can be any input/output module. Exemplary input/output modules710include data ports such as USB ports. The input/output module710is configured to connect to a communications module712. Exemplary communications modules712(e.g., communications modules218) include networking interface cards, such as Ethernet cards and modems. In certain aspects, input/output module710is configured to connect to a plurality of devices, such as an input device714(e.g., input device214) and/or an output device716(e.g., output device216). Exemplary input devices714include a keyboard and a pointing device, e.g., a mouse or a trackball, by which a user can provide input to the computer system700. Other kinds of input devices714can be used to provide for interaction with a user as well, such as a tactile input device, visual input device, audio input device, or brain-computer interface device. For example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, tactile, or brain wave input. Exemplary output devices716include display devices, such as an LCD (liquid crystal display) monitor, for displaying information to the user.

According to one aspect of the present disclosure, the client device110and server130can be implemented using a computer system700in response to processor702executing one or more sequences of one or more instructions contained in memory704. Such instructions may be read into memory704from another machine-readable medium, such as data storage device706. Execution of the sequences of instructions contained in main memory704causes processor702to perform the process steps described herein. One or more processors in a multi-processing arrangement may also be employed to execute the sequences of instructions contained in memory704. In alternative aspects, hard-wired circuitry may be used in place of or in combination with software instructions to implement various aspects of the present disclosure. Thus, aspects of the present disclosure are not limited to any specific combination of hardware circuitry and software.