diff --git a/aws.html b/aws.html index 0071af271..738ee630b 100644 --- a/aws.html +++ b/aws.html @@ -107,6 +107,9 @@ $(addBlockSwitches);

2.1.0.BUILD-SNAPSHOT

+

The AWS adapter takes a Spring Cloud Function app and converts it to a form that can run in AWS Lambda.

diff --git a/azure.html b/azure.html index 99e0bc83f..6943fe52e 100644 --- a/azure.html +++ b/azure.html @@ -101,6 +101,9 @@ $(addBlockSwitches);

2.1.0.BUILD-SNAPSHOT

+

The Azure adapter bootstraps a Spring Cloud Function context and channels function calls from the Azure framework into the user functions, using Spring Boot configuration where necessary. Azure Functions has quite a unique, but invasive programming model, involving annotations in user code that are specific to the platform. The easiest way to use it with Spring Cloud is to extend a base class and write a method in it with the @FunctionName annotation which delegates to a base class method.

diff --git a/openwhisk.html b/openwhisk.html index 998bdde6f..d4b323ac7 100644 --- a/openwhisk.html +++ b/openwhisk.html @@ -98,6 +98,9 @@ $(addBlockSwitches);

2.1.0.BUILD-SNAPSHOT

+

The OpenWhisk adapter is in the form of an executable jar that can be used in a a docker image to be deployed to Openwhisk. The platform works in request-response mode, listening on port 8080 on a specific endpoint, so the adapter is a simple Spring MVC application.