Hello World Application

We'll show here how to build an "Hello World" workflow from scratch, with the following steps:

  • create a project
  • write tasks
  • write a workflow
  • deploy workers
  • run a workflow

The workflow HelloWorld will take a name string as input and return "Hello $name!" using sequentially 2 tasks run on distributed workers:

  • a sayHello task that takes a name string as input and returns "Hello $name"
  • an addEnthusiasm task that takes a str string as input and returns "$str!"


We need to have Gradle installed, with:

  • an Apache Pulsar cluster (install)
  • a Redis (install) or MySQL database, to store workflow states.

If we have Docker on our computer, we can simply run docker-compose up on this docker-compose.yml file:

  # Pulsar settings
    image: apachepulsar/pulsar:2.10.0
      - BOOKIE_MEM=" -Xms512m -Xmx512m -XX:MaxDirectMemorySize=1g"
    command: >
      /bin/bash -c "bin/apply-config-from-env.py conf/standalone.conf && bin/pulsar standalone"
      - "pulsardata:/pulsar/data"
      - "pulsarconf:/pulsar/conf"
      - "6650:6650"
      - "8080:8080"
      - "8081:8081"

  # Redis storage for state persistence
    image: redis:6.0-alpine
      - "6379:6379"
      - "redisdata:/data"


Create project

Create a new project within a new directory:

mkdir hello-world && cd hello-world && gradle init

Configure this project:

Select type of project to generate:
  1: basic
  2: application
  3: library
  4: Gradle plugin
Enter selection (default: basic) [1..4] 2

Select implementation language:
  1: C++
  2: Groovy
  3: Java
  4: Kotlin
  5: Swift
Enter selection (default: Java) [1..5] 3

Split functionality across multiple subprojects?:
  1: no - only one application project
  2: yes - application and library projects
Enter selection (default: no - only one application project) [1..2] 1

Select build script DSL:
  1: Groovy
  2: Kotlin
Enter selection (default: Kotlin) [1..2] 1

Project name (default: hello-world):
Source package (default: hello.world):

in our build gradle file, we add:

  • Maven repository
  • needed dependencies
  • instruction to compile to Java 1.8

And install dependencies:

./gradlew install

Writing services

Let's create a services directory:

mkdir app/src/main/java/hello/world/services

in which, we add a HelloWorldService interface:

and a HelloWorldServiceImpl implementation:

Writing workflow

Let's create a workflows directory:

mkdir app/src/main/java/hello/world/workflows

in which, we add a HelloWorldWorkflow interface:

and a HelloWorldWorkflowImpl implementation:

Workflow implementation must extend io.infinitic.workflows.Workflow

Note the newService function creating a stub from the HelloWorldService interface. From a syntax point of view, this stub can be used as an implementation of HelloWorldService . But instead of executing a method, it sends a message to Infinitic requesting this execution. That's why nothing happens if we run a workflow without having deployed any worker.

Pulsar configuration

The app/infinitic.yml file should contain the Pulsar configuration:

  brokerServiceUrl: pulsar://localhost:6650
  webServiceUrl: http://localhost:8080
  tenant: infinitic
  namespace: dev

Deploying workers

The easiest way to build workers is from an app/infinitic.yml config file:

    host: localhost
    port: 6379
    database: 0

  brokerServiceUrl: pulsar://localhost:6650
  tenant: infinitic
  namespace: dev

  - name: hello.world.services.HelloWorldService
    class: hello.world.services.HelloWorldServiceImpl

  - name: hello.world.workflows.HelloWorld
    class: hello.world.workflows.HelloWorldImpl

Please update values for Redis and Pulsar connections if necessary.

Then, to create a worker, just replace the App file with:

Our app is ready to run as a worker:

./gradlew run

We have a working worker listening Pulsar and waiting for instructions:

> Task :run
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

The SLF4J outputs are there because we do not have any logger yet in the app. To remove those messages, add our logger of choice (for example [Simple Logger] (#simple-logger) as a dependency in our Gradle build file.

When coding, workers need to be restarted to account for any change.

Start a workflow

The easiest way to instantiate an InfiniticClient is to use a config file exposing a pulsar configuration. Here, we already have the infinitic.yml file that we can reuse in a new Client file:

We can run it directly from our IDE (we may need to change the working directory on the Run configuration), or add the startWorkflow Gradle task to our build file:

and run it from the command line:

./gradlew startWorkflow --args Infinitic

Where our app/worker is running, we should see:

Hello Infinitic!

Congrats! We have run our first Infinitic workflows.



Here is a check-list when encountering issues:

  • Pulsar should be up and running
  • Redis should be up and running
  • infinitic.yml file:
    • should expose correct values to access Pulsar and Redis
    • should have name and class that match interface names and implementation full names respectively of our task and workflows
    • should have at least 1 taskEngine consumer, 1 workflowEngine consumer
  • at least one worker should be running

If nothing happens when it should not, remember that workers won't quit if an exception is thrown from our tasks or workflows. To see exceptions, we must install a logger and look at the log file.

Simple logger

To use SimpleLogger as logger in this app, just add the dependency in our Gradle build file:

and this simplelogger.properties example file in our resources directory:

# SLF4J's SimpleLogger configuration file
# Simple implementation of Logger that sends all enabled log messages, for all defined loggers, to System.err.

# Uncomment this line to use a log file

# Default logging detail level for all instances of SimpleLogger.
# Must be one of ("trace", "debug", "info", "warn", or "error").
# If not specified, defaults to "info".

# Set to true if you want the current date and time to be included in output messages.
# Default is false, and will output the number of milliseconds elapsed since startup.

# Set to true if you want to output the current thread name.
# Defaults to true.

# Set to true if you want the last component of the name to be included in output messages.
# Defaults to false.

Working repository

If we fail to chase a bug, we still can copy this working repository and look for the differences:

git clone https://github.com/infiniticio/infinitic-example-java-hello-world

New version 0.11.2!