Spring Cloud Function features:
Wrappers for @Beans of type Function, Consumer and
-Supplier, exposing them to the outside world as either HTTP
-endpoints and/or message stream listeners/publishers with RabbitMQ, Kafka etc.
Choice of programming styles - reactive, imperative or hybrid.
Compiling strings which are Java function bodies into bytecode, and
-then turning them into @Beans that can be wrapped as above.
Function composition and adaptation (e.g., composing imperative functions with reactive).
Deploying a JAR file containing such an application context with an -isolated classloader, so that you can pack them together in a single -JVM.
+Support for reactive function with multiple inputs and outputs allowing merging, joining and other complex streaming operation to be handled by functions.
Adapters for AWS Lambda, Microsoft Azure, Apache OpenWhisk and possibly other "serverless" service providers.
+Transparent type conversion of inputs and outputs.
Packaging functions for deployments, specific to the target platform (e.g., Project Riff, AWS Lambda and more)
+Adapters to expose function to the outside world as HTTP endpoints etc.
+Deploying a JAR file containing such an application context with an isolated classloader, so that you can pack them together in a single JVM.
+Compiling strings which are Java function bodies into bytecode, and then turning them into @Beans that can be wrapped as above.
Adapters for AWS Lambda, Microsoft Azure, Apache OpenWhisk and possibly other "serverless" service providers.
+Here’s a complete, executable, testable Spring Boot application (implementing a simple string manipulation):