Understanding the execution of application Inside Openwhisk
With the demo application in place, it's time for us to understand how the execution of this application works behind the scenes.
Behind the successful execution of the application, there are several steps involved which start from the wsk action invoke command that we ran to execute our application. So, let's take a look at the steps that happened behind the scenes:
- Making the API call: Every action that we build to deploy on OpenWhisk is mapped as an API endpoint that will invoke the action. When we run
wsk action invoke, the command makes a call to the API endpoint that has been mapped for the provided function. This call is then intercepted by Nginx inside OpenWhisk, which acts as a termination point for SSL and then invokes the controller. - Processing by the controller: The controller, which is an implementation of the REST API, disambiguates what the request is supposed to do based on the HTTP method used for the request. Once...
