<p>The <ahref="https://aws.amazon.com/">AWS</a> adapter takes a Spring Cloud Function app and converts it to a form that can run in AWS Lambda.</p>
@@ -376,7 +376,7 @@ we will not attempt any conversion and will pass the raw input directly to a fun
<divclass="paragraph">
<p>Your functions will start much quicker if you can use functional bean definitions instead of <code>@Bean</code>. To do this make your main class
an <code>ApplicationContextInitializer<GenericApplicationContext></code> and use the <code>registerBean()</code> methods in <code>GenericApplicationContext</code> to
create all the beans you need. You function need sto be registered as a bean of type <code>FunctionRegistration</code> so that the input and
create all the beans you need. You function need to be registered as a bean of type <code>FunctionRegistration</code> so that the input and
output types can be accessed by the framework. There is an example in github (the AWS sample is written in this style). It would
<p>The <ahref="https://azure.microsoft.com">Azure</a> 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 <code>@FunctionName</code> annotation which delegates to a base class method.</p>
<p>The <ahref="https://openwhisk.apache.org/">OpenWhisk</a> 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.</p>
<li><ahref="#_standalone_web_applications">Standalone Web Applications</a></li>
@@ -135,7 +136,7 @@ $(addBlockSwitches);
<p>Mark Fisher, Dave Syer, Oleg Zhurakousky, Anshul Mehra</p>
</div>
<divclass="paragraph">
<p><strong>3.0.0.BUILD-SNAPSHOT</strong></p>
<p><strong>3.0.1.BUILD-SNAPSHOT</strong></p>
</div>
<hr>
</div>
@@ -299,126 +300,51 @@ string like that.)</p>
</div>
</div>
<divclass="sect1">
<h2id="_building_and_running_a_function"><aclass="link"href="#_building_and_running_a_function">Building and Running a Function</a></h2>
<divclass="sectionbody">
<divclass="paragraph">
<p>The sample <code>@SpringBootApplication</code> above has a function that can be
decorated at runtime by Spring Cloud Function to be an HTTP endpoint,
or a Stream processor, for instance with RabbitMQ, Apache Kafka or
JMS.</p>
</div>
<divclass="paragraph">
<p>The <code>@Beans</code> can be <code>Function</code>, <code>Consumer</code> or <code>Supplier</code> (all from
<code>java.util</code>), and their parametric types can be String or POJO.</p>
</div>
<divclass="paragraph">
<p>Functions can also be of <code>Flux<String></code> or <code>Flux<Pojo></code> and Spring
Cloud Function takes care of converting the data to and from the
desired types, as long as it comes in as plain text or (in the case of
the POJO) JSON. There is also support for <code>Message<Pojo></code> where the
message headers are copied from the incoming event, depending on the
adapter. The web adapter also supports conversion from form-encoded
data to a <code>Map</code>, and if you are using the function with Spring Cloud
Stream then all the conversion and coercion features for message
payloads will be applicable as well.</p>
</div>
<divclass="paragraph">
<p>Functions can be grouped together in a single application, or deployed
one-per-jar. It’s up to the developer to choose. An app with multiple
functions can be deployed multiple times in different "personalities",
exposing different functions over different physical transports.</p>
</div>
</div>
</div>
<divclass="sect1">
<h2id="_function_catalog_and_flexible_function_signatures"><aclass="link"href="#_function_catalog_and_flexible_function_signatures">Function Catalog and Flexible Function Signatures</a></h2>
<h3id="_function_catalog_and_flexible_function_signatures"><aclass="link"href="#_function_catalog_and_flexible_function_signatures">Function Catalog and Flexible Function Signatures</a></h3>
<divclass="paragraph">
<p>One of the main features of Spring Cloud Function is to adapt and support a range of type signatures for user-defined functions,
while providing a consistent execution model.
That’s why all user defined functions are transformed into a canonical representation by <code>FunctionCatalog</code>, using primitives
defined by the <ahref="https://projectreactor.io/">Project Reactor</a> (i.e., <code>Flux<T></code> and <code>Mono<T></code>).
Users can supply a bean of type <code>Function<String,String></code>, for instance, and the <code>FunctionCatalog</code> will wrap it into a
Function<String, String> function = catalog.lookup("uppercase");
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
buildmaster