diff --git a/aws.html b/aws.html index 738ee630b..301bd92ab 100644 --- a/aws.html +++ b/aws.html @@ -108,7 +108,7 @@ $(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 6943fe52e..a0d7e697e 100644 --- a/azure.html +++ b/azure.html @@ -102,7 +102,7 @@ $(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 d4b323ac7..4d3b59478 100644 --- a/openwhisk.html +++ b/openwhisk.html @@ -99,7 +99,7 @@ $(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.

diff --git a/spring-cloud-function.html b/spring-cloud-function.html index e80264917..282861f93 100644 --- a/spring-cloud-function.html +++ b/spring-cloud-function.html @@ -124,7 +124,7 @@ $(addBlockSwitches);