Master Advanced Spring Cloud Function Techniques in Spring Boot

Overview

Spring Cloud Function aims to simplify business logic implementation by providing function‑centric capabilities that decouple the development lifecycle from any specific runtime target, allowing the same code to run as a web endpoint, stream processor, or task. It supports a unified programming model across serverless providers and can run independently (locally or in PaaS).

Advanced Examples

2.1 HTTP Request Parameters

In Spring Cloud Function, HTTP request parameters are stored in the message header http_request_param as a map. To access them, the function should accept a Message<String> type.

@Bean
public Function<Message<String>, String> params() {
  return message -> {
    System.out.println(message.getHeaders());
    return String.format("你输入的参数：%s", message.getHeaders().get(HeaderUtils.HTTP_REQUEST_PARAM));
  };
}

Console output example:

{http_request_param={name=admin, age=33}, Accept=text/html,application/xhtml+xml,application/xml;q=0.9,..., uri=http://localhost:8080/params?name=admin&age=33, ...}

2.2 Function Mapping Rules

When multiple functions exist, each is exported with its name as part of the path (e.g., localhost:8080/uppercase). You can map specific functions or compositions to the root path using spring.cloud.function.definition:

spring:
  cloud:
    function:
      definition: length|reverse

Defining this property also maps unknown URIs to the root path.

2.3 Function Filtering Rules

To export only selected functions, list them (separated by ;) in spring.cloud.function.definition. Functions not listed, including compositions, will not be exported.

--spring.cloud.function.definition=uppercase;reverse

After this configuration, length and split are inaccessible.

--spring.cloud.function.definition=length|reverse;length

This configuration also prevents access to split.

2.4 Functional Bean Definition

Spring Cloud Function supports a functional bean style, suitable for lightweight applications. The functional bean style replaces @SpringBootApplication with @SpringBootConfiguration and uses FunctionalSpringApplication instead of the standard SpringApplication.

@SpringBootConfiguration
public class SpringcloudFunction2Application implements ApplicationContextInitializer<GenericApplicationContext> {

  public static void main(String[] args) {
    FunctionalSpringApplication.run(SpringcloudFunction2Application.class, args);
  }

  @Override
  public void initialize(GenericApplicationContext context) {
    context.registerBean("split", FunctionRegistration.class, () -> {
      CustomFunction target = new CustomFunction();
      FunctionRegistration<CustomFunction> split = new FunctionRegistration<>(target, "split");
      split.type(CustomFunction.class);
      return split;
    });
  }
}

2.5 Function Visualization and Control

Spring Cloud Function can expose available functions via Actuator endpoints or programmatically.

Programmatic way :

@Resource
private FunctionCatalog functionCatalog;

@Bean
public Function<Mono<String>, Flux<String>> funs() {
  return type -> Flux.fromIterable(functionCatalog.getNames(null));
}

Browser output shows the list of function names.

Actuator way (enable the endpoint):

management:
  endpoints:
    web:
      exposure:
        include:
        - functions

2.6 Function Scanning

Spring Cloud Function scans the functions package for implementations of Function, Consumer, and Supplier. To change the package, set spring.cloud.function.scan.packages:

spring:
  cloud:
    function:
      scan:
        packages: com.pack.functions

Scanning can be disabled:

spring:
  cloud:
    function:
      scan:
        enabled: false

Finished!