Batch Processing with Spring Cloud Task

In this guide, we develop a Spring Boot application that uses Spring Cloud Task and deploy it to Cloud Foundry, Kubernetes, and your local machine. In another guide, we deploy the Task application by using Data Flow.

The following sections describe how to build this application from scratch. If you prefer, you can download a zip file that contains the sources for the application (called billsetup), unzip it, and proceed to the deployment step.

You can download the project from your browser or by running the following command, from the command-line:

wget "" -O


We start from the Spring Initializr and create a Spring Cloud Task application.

Suppose a cell phone data provider needs to create billing statements for customers. The usage data is stored in JSON files that are stored on the file system. The billing solution must pull data from these files, generate the billing data from this usage data, and store it in a BILLING_STATEMENTS table.

For this example, we break up the solution into two phases:

  1. billsetuptask: The billsetuptask application is a Spring Boot application that uses Spring Cloud Task to create the BILL_STATEMENTS table.
  2. billrun: The billrun application is a Spring Boot application that uses Spring Cloud Task and Spring Batch to read usage data and price for each row from a JSON file and put the resulting data into the BILL_STATEMENTS table.

For this section, we create a Spring Cloud Task and Boot application that creates the BILL_STATEMENTS table that are used by the BillRun application. The following image shows the BILL_STATEMENTS table:



Follow these steps to create the app:

  1. Visit the Spring Initialzr site.
  2. Select the latest 2.7.x release of Spring Boot.
  3. Create a new Maven project with a Group name of io.spring and an Artifact name of billsetuptask.
  4. In the Dependencies text box, type task and then select the Cloud Task dependency.
  5. In the Dependencies text box, type jdbc and then select the JDBC API dependency.
  6. In the Dependencies text box, type h2 and then select the H2 dependency. We use H2 for unit testing.
  7. In the Dependencies text box, type mariadb and then select the MariaDB dependency.
  8. Click the Generate Project button.

Now you should unzip the file and import the project into your favorite IDE.

Setting up MariaDB

Follow these instructions to run a MariaDB docker image for this example:

  1. Pull a MariaDB docker image by running the following command:

    docker pull mariadb:10.4.22
  2. Start MariaDB by running the following command:

    docker run --name mariadb -d -p 3306:3306 -e MARIADB_ROOT_PASSWORD=password -e MARIADB_DATABASE=task mariadb:10.4.22

Building the Application

Now we can create the code required for this application. To do so:

  1. Create the io.spring.billsetuptask.configuration package.
  2. In the io.spring.billsetuptask.configuration package, create a TaskConfiguration class that resembles the following listing:
import javax.sql.DataSource;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.CommandLineRunner;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.jdbc.core.JdbcTemplate;

public class TaskConfiguration {

   private DataSource dataSource;

   public CommandLineRunner commandLineRunner() {
      return args -> {
         JdbcTemplate jdbcTemplate = new JdbcTemplate(dataSource);
         jdbcTemplate.execute("CREATE TABLE IF NOT EXISTS BILL_STATEMENTS ( id int, " +
                 "first_name varchar(50), last_name varchar(50), minutes int, " +
                 "data_usage int, bill_amount decimal(10,2))");

The @EnableTask annotation sets up a TaskRepository, which stores information about the task execution (such as the start and end time of the task and the exit code).


Now we can create our test. To do so, update the Initialzr auto-generated with the following code:

package io.spring.billsetuptask;

import org.junit.jupiter.api.Test;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.jdbc.core.JdbcTemplate;

import javax.sql.DataSource;

import static org.assertj.core.api.Assertions.assertThat;

class BillSetupTaskApplicationTests {

	private DataSource dataSource;

	public void testRepository() {
		JdbcTemplate jdbcTemplate = new JdbcTemplate(this.dataSource);
		int result = jdbcTemplate.queryForObject(


Run this test in your IDE. Since Spring Boot's spring.datasource properties are not set, the test runs against the embedded H2 database. In the next step, you can deploy the application and target a MariaDB database.


In this section, we deploy the task application to the local machine, Cloud Foundry, and Kubernetes.


Now we can build the project. To do so:

  1. From the command line, change directory to the location of your project and build the project by running the following Maven command: ./mvnw clean package
  2. Run the application with the configuration required to create the BILL_STATEMENTS table in the MariaDB database. To configure how the billsetuptask application runs, you can use the following arguments:

    1. spring.datasource.url: Set the URL to your database instance. In the following sample, we connect to a MariaDB task database on our local machine at port 3306.
    2. spring.datasource.username: The user name to be used for the MariaDB database. In the following sample, it is root.
    3. spring.datasource.password: The password to be used for the MariaDB database. In the following sample. it is password.
    4. spring.datasource.driverClassName: The driver to use to connect to the MariaDB database. In the following sample, it is `org.mariadb.jdbc.Driver.

    The following command runs the billsetuptask application with our database connection values:

    java -jar target/billsetuptask-0.0.1-SNAPSHOT.jar \
    --spring.datasource.url=jdbc:mariadb://localhost:3306/task \
    --spring.datasource.username=root \
    --spring.datasource.password=password \

    Alternatively, you can place these properties in and run the BillSetupTaskApplication from your IDE.

Viewing the Results of Task Execution in the Database

Spring Cloud Task records all task executions to a table called TASK_EXECUTION. Here is some of the information that is recorded by Spring Cloud Task:

  • START_TIME: The time at which the task execution started
  • END_TIME: The time at which the task execution completed
  • TASK_NAME: The name associated with the task execution
  • EXIT_CODE: The exit code that was returned by the task execution
  • EXIT_MESSAGE: The exit message that was returned for the execution
  • ERROR_MESSAGE: The error message (if any) that was returned for the execution
  • EXTERNAL_EXECUTION_ID: An ID to be associated with the task execution

By default, the TASK_NAME is application.

You can use the following commands to query the TASK_EXECUTION table:

docker exec -it mariadb bash -l
# mariadb -u root -ppassword
MariaDB> select * from task.TASK_EXECUTION;

The results should resemble the following output:

|                 1 | 2019-04-23 18:10:57 | 2019-04-23 18:10:57 | application     |         0 | NULL         | NULL          | 2019-04-23 18:10:57 | NULL                  |                NULL |

Setting the Application Name for Task Execution

In the previous table, the TASK_NAME column has the default value of application. Spring Cloud Task lets us change this setting by using the To do so, we add that property to our next run, as follows:

java -jar target/billsetuptask-0.0.1-SNAPSHOT.jar \
--spring.datasource.url=jdbc:mariadb://localhost:3306/task \
--spring.datasource.username=root \
--spring.datasource.password=password \
--spring.datasource.driverClassName=org.mariadb.jdbc.Driver \

Now, when you query the table, you can see that the last task run in the query now has a name of BillSetupTest1.


To stop and remove the MariaDB container that is running in the docker instance, run the following command:

docker stop mariadb
docker rm mariadb

Cloud Foundry

This guide walks through how to deploy and run simple spring-cloud-task stand-alone applications to Cloud Foundry.


On your local machine, you need to have installed the following:

You also need to have installed the Cloud Foundry command line interface (see the documentation).

Building the Application

Now we can build the project. To do so, from a command line, change directory to the location of your project and build the project by running the following Maven command: ./mvnw clean package

Setting up Cloud Foundry

First, you need a Cloud Foundry account. You can create a free account by using Pivotal Web Services (PWS). We use PWS for this example. If you use a different provider, your experience may slightly vary from this description.

To log into Cloud Foundry from the Cloud Foundry command line interface, run the following command:

cf login

You can also target specific Cloud Foundry instances with the -a flag — for example, cf login -a

Before you push an application, you should also ensure that you setup the MySQL Service on Cloud Foundry. You can check what services are available by running the following command:

cf marketplace

On Pivotal Web Services (PWS), you should be able to use the following command to install the MySQL service:

cf create-service cleardb spark task-example-mysql

Make sure you name your MySQL service task-example-mysql. The rest of this example uses that value.

Task Concepts in Cloud Foundry

To provide configuration parameters for Cloud Foundry, we create dedicated manifest YAML files for each application.

For additional information on setting up a manifest, see the Cloud Foundry documentation

Running tasks on Cloud Foundry is a two-stage process. Before you can actually run any tasks, you need to first push an app that is staged without any running instances. We provide the following common properties to the manifest YAML file to each application:

memory: 32M
health-check-type: process
no-route: true
instances: 0

The key is to set the instances property to 0. Doing so ensures that the application is staged without actually being run. We also do not need a route to be created and can set no-route to true.

Having this app staged but not running has a second advantage as well. Not only do we need this staged application to run a task in a subsequent step, but, if our database service is internal (part of your Cloud Foundry instance), we can use this application to establish an SSH tunnel to the associated MySQL database service to see the persisted data. We go into the details for that later in this document.

Running billsetuptask on Cloud Foundry

To deploy the first task application (billsetuptask), you must create a file named manifest-billsetuptask.yml with the following contents:

  - name: billsetuptask
    memory: 32M
    health-check-type: process
    no-route: true
    instances: 0
    disk_quota: 1G
    timeout: 180
      - java_buildpack
    path: target/billsetuptask-0.0.1-SNAPSHOT.jar
      - task-example-mysql

Now you can run cf push -f ./manifest-billsetuptask.yml. Doing so stages the application, and the application should be up. You can verify that the application is up in the Cloud Foundry dashboard, as follows:

billsetuptask deployed to Cloud Foundry

You can now run the task. To do so:

cf run-task billsetuptask ".java-buildpack/open_jdk_jre/bin/java org.springframework.boot.loader.JarLauncher arg1" --name billsetuptask-task

You can specify the following optional arguments:

  • -k Disk limit (e.g. 256M, 1024M, 1G)
  • -m Memory limit (e.g. 256M, 1024M, 1G)

The task should execute successfuly. You can verify the results in the Cloud Foundry dashboard by clicking on the Task tab, as follows:

Cloud Foundry Dashboard Task Tab

In the Tasks table, you should see your task billsetuptask with a State of Succeeded, as follows:

billsetuptask executed on Cloud Foundry

Removing All Task Applications and Services

With the conclusion of this example, if you do not plan to proceed to the Spring Batch example, you may want to remove all instances on Cloud Foundry. To do so, run the following commands:

cf delete billsetuptask -f
cf delete-service task-example-mysql -f


This section walks through how to deploy and run a simple spring-cloud-task application on Kubernetes.

We deploy the billsetuptask sample application to Kubernetes.

Setting up the Kubernetes Cluster

We need a running Kubernetes cluster. For this example, we deploy to minikube.

Verifying that Minikube is Running

To verify that Minikube is running, run the following command (shown with its output):

minikube status

host: Running
kubelet: Running
apiserver: Running
kubectl: Correctly Configured: pointing to minikube-vm at
Installing the Database

You need to install a MariaDB server by using the default configuration from Spring Cloud Data Flow. To do so, run the following command:

kubectl apply -f \
-f \
-f \
Building a Docker image

We need to build the docker image for the billsetuptask application. To do so, we use Spring Boot to create the image.

You can add the image to the minikube Docker registry. To do so, run the following commands:

eval $(minikube docker-env)
./mvnw spring-boot:build-image

You can run the following command to verify its presence (by finding springcloudtask/billsetuptask in the resulting list of images):

docker images
Deploying the Application

The simplest way to deploy a task application is as a standalone Pod. Deploying tasks as a Job or CronJob is considered best practice for production environments but is beyond the scope of this guide.

First, save the following content to task-app.yaml:

apiVersion: v1
kind: Pod
  name: billsetuptask
  restartPolicy: Never
    - name: task
      image: springcloudtask/billsetuptask:0.0.1-SNAPSHOT
              name: mariadb
              key: mariadb-root-password
          value: jdbc:mariadb://mariadb:3306/task
          value: root
          value: org.mariadb.jdbc.Driver
    - name: init-mariadb-database
      image: mariadb:10.4.22
        - name: MARIADB_PWD
              name: mariadb
              key: mariadb-root-password
          'mariadb -h mariadb -u root --password=$MARIADB_PWD -e "CREATE DATABASE IF NOT EXISTS task;"',

Now you can start the application by running the following command:

kubectl apply -f task-app.yaml

When the task is complete, you should see output that resembles the following:

kubectl get pods
NAME                     READY   STATUS      RESTARTS   AGE
mariadb-5cbb6c49f7-ntg2l 1/1     Running     0          4h
billsetuptask            0/1     Completed   0          81s

Once you are satisfied with the results, you can delete the pod. To do so, run the following command:

kubectl delete -f task-app.yaml

Now you can examine the database to see the results of running the application. To do so, log in to the mariadb container and query the TASK_EXECUTION table. Get the name of the MariaDB pod by running kubectl get pods, as shown earlier. Then you need to log in, as follows:

kubectl exec -it mariadb-5cbb6c49f7-ntg2l -- /bin/bash
# mariadb -u root -p$MARIADB_ROOT_PASSWORD
mariadb> select * from task.TASK_EXECUTION;

To uninstall mariadb, run the following command:

kubectl delete all -l app=mariadb

What's Next?

Congratulations! You have created and deployed a Spring Cloud Task application. Now you can go on to the next section and create a Spring Batch Application.