Dapr SDK for Java

This is the Dapr SDK for Java, including the following features:

• PubSub
• Service Invocation
• Binding
• State Store
• Actors
• Workflows

Getting Started

Pre-Requisites

• SDKMAN! installed (recommended):
  • SDKMAN!
• Java IDE installed:
  • IntelliJ
  • Eclipse
  • Apache NetBeans
  • Visual Studio Code
  • Any other IDE for Java that you prefer.
• Install one of the following build tools for Java:
  • Maven 3.x
  • Gradle 6.x
• If needed, install the corresponding plugin for the build tool in your IDE, for example:
  • Maven in IntelliJ
  • Gradle in IntelliJ
  • Maven in Eclipse with m2e
  • Gradle in Eclipse with Buildship
• An existing Java Maven or Gradle project. You may also start a new project via one of the options below:
  • New Maven project in IntelliJ
  • Maven in 5 minutes
  • Install toxiproxy-server binary

Install JDK

If using SDKMAN!, execute sdk env install to install the required JDK.

Importing Dapr's Java SDK

For a Maven project, add the following to your pom.xml file:

<project>
  ...
  <dependencies>
    ...
     <!-- Dapr's core SDK with all features, except Actors. -->
    <dependency>
      <groupId>io.dapr</groupId>
      <artifactId>dapr-sdk</artifactId>
      <version>1.14.1</version>
    </dependency>
    <!-- Dapr's SDK for Actors (optional). -->
    <dependency>
      <groupId>io.dapr</groupId>
      <artifactId>dapr-sdk-actors</artifactId>
      <version>1.14.1</version>
    </dependency>
    <!-- Dapr's SDK integration with SpringBoot (optional). -->
    <dependency>
      <groupId>io.dapr</groupId>
      <artifactId>dapr-sdk-springboot</artifactId>
      <version>1.14.1</version>
    </dependency>
    ...
  </dependencies>
  ...
</project>

For a Gradle project, add the following to your build.gradle file:

dependencies {
...
    // Dapr's core SDK with all features, except Actors.
    compile('io.dapr:dapr-sdk:1.14.1')
    // Dapr's SDK for Actors (optional).
    compile('io.dapr:dapr-sdk-actors:1.14.1')
    // Dapr's SDK integration with SpringBoot (optional).
    compile('io.dapr:dapr-sdk-springboot:1.14.1')
}

Running the examples

Clone this repository including the submodules:

git clone https://github.com/dapr/java-sdk.git

Then head over to build the Maven (Apache Maven version 3.x) project:

# make sure you are in the `java-sdk` directory.
./mvnw clean install

Try the following examples to learn more about Dapr's Java SDK:

• Invoking a Http service
• Invoking a Grpc service
• State management
• PubSub with subscriber
• PubSub with streaming subscription
• Binding with input over Http
• Actors
• Workflows
• Secrets management
• Configuration
• Distributed tracing with OpenTelemetry SDK
• Exception handling
• Unit testing

Running Spring Boot examples

The Spring Boot integration for Dapr use Testcontainers to set up a local environment development flow that doesn't require the use of the dapr CLI and it integrates with the Spring Boot programming model.

You can find a step-by-step tutorial showing this integration here.

API Documentation

Please, refer to our Javadoc website.

Reactor API

The Java SDK for Dapr is built using Project Reactor. It provides an asynchronous API for Java. A result is consumed synchronously by using the block() method, as shown in the examples referenced above.

The code below does not make any API call, it simply returns the Mono publisher object. Nothing happens until the application subscribes or blocks on the result:

Mono<Void> result = daprClient.publishEvent("mytopic", "my message");

To start execution and receive the result object synchronously (void or Void becomes an empty result), use block(). The code below shows how to execute the call and consume an empty response:

Mono<Void> result = daprClient.publishEvent("mytopic", "my message");
result.block();

How to use a custom serializer

This SDK provides a basic serialization for request/response objects, and state objects. Applications should provide their own serialization for production scenarios.

1. Implement the DaprObjectSerializer interface. See this class as an example.
2. Use your serializer class in the following scenarios:
   • When building a new instance of DaprClient:

   DaprClient client = (new DaprClientBuilder())
       .withObjectSerializer(new MyObjectSerializer()) // for request/response objects.
       .withStateSerializer(new MyStateSerializer()) // for state objects.
       .build();
   

   • When registering an Actor Type:

   ActorRuntime.getInstance().registerActor(
     DemoActorImpl.class,
     new MyObjectSerializer(), // for request/response objects.
     new MyStateSerializer()); // for state objects.
   

   • When building a new instance of ActorProxy to invoke an Actor instance, use the same serializer as when registering the Actor Type:

   try (ActorClient actorClient = new ActorClient()) {
     DemoActor actor = (new ActorProxyBuilder(DemoActor.class, actorClient))
         .withObjectSerializer(new MyObjectSerializer()) // for request/response objects.
         .build(new ActorId("100"));
   }
   

Debug a Java application or Dapr's Java SDK

In IntelliJ Community Edition, consider debugging in IntelliJ.

In Visual Studio Code, consider debugging in Visual Studio Code.

If you need to debug your Application, run the Dapr sidecar separately, and then start the application from your IDE (IntelliJ or Eclipse, for example). For Linux and MacOS:

dapr run --app-id testapp --app-port 3000 --dapr-http-port 3500 --dapr-grpc-port 5001

Note: confirm the correct port that the app will listen to and that the Dapr ports above are free, changing the ports if necessary.

When running your Java application from your IDE, make sure the following environment variables are set, so the Java SDK knows how to connect to Dapr's sidecar:

DAPR_HTTP_PORT=3500
DAPR_GRPC_PORT=5001

Now you can go to your IDE and debug your Java application, using port 3500 to call Dapr while also listening to port 3000 to expose Dapr's callback endpoint.

Exception handling

Most exceptions thrown from the SDK are instances of DaprException. DaprException extends from RuntimeException, making it compatible with Project Reactor. See the exception example for more details.

Development

Update URL to fetch proto files

Change the dapr.proto.baseurl property below in pom.xml to point to the URL for the desired commit hash in Git if you need to target a proto file that is not been merged into master yet.

Note: You may need to run ./mvnw clean after changing this setting to remove any auto-generated files so that the new proto files get downloaded and compiled.

<project>
  ...
  <properties>
    ...
    <!-- change this .... -->
    <dapr.proto.baseurl>https://raw.githubusercontent.com/dapr/dapr/(current ref in pom.xml)/dapr/proto</dapr.proto.baseurl>
    <!-- to something like this: -->
    <dapr.proto.baseurl>https://raw.githubusercontent.com/dapr/dapr/1ac5d0e8590a7d6772c9957c236351ed992ccb19/dapr/proto</dapr.proto.baseurl>
    ...
  </properties>
  ...
</project>

Running Integration Tests (ITs)

Pre-Requisites

• Pre-Requisites for the SDK
• Docker installed
  • Docker Compose
  • Docker Desktop
• Bash shell
  • In Windows use WSL2
  • In Linux and Mac, default shells are enough

Code

The code for the tests are present inside the project sdk-tests. This module alone can be imported as a separate project in IDEs. This project depends on the rest of the JARs built by the other modules in the repo like sdk, sdk-springboot etc.

As a starting point for running the Integration Tests, first run ./mvnw clean install from the root of the repo to build the JARs for the different modules, except the sdk-tests module.

Run all the dependent services spun up during build

During normal CI build, docker compose is used to bring up services like MongoDB, Hashicorp Vault, Apache Zookeeper, Kafka etc.

Similarly, all of these need to be run for running the ITs either individually or as a whole.

Run the following commands from the root of the repo to start all the docker containers that the tests depend on.

docker compose -f ./sdk-tests/deploy/local-test.yml up -d

To stop the containers and services, run the following commands.

docker compose -f ./sdk-tests/deploy/local-test.yml down

Run all ITs from command line

From the java-sdk repo root, change to the sdk-tests directory and run the following command.

## with current directory as /java-sdk/sdk-tests/

../mvnw clean install

The above command runs all the integration tests present in the sdk-tests project.

Run Individual tests from IntelliJ

In IntelliJ, go to File > New > Project from Existing Sources.... Import the sdk-tests project.

Once the project has been imported, the individual tests can be run normally as any Unit Tests, from the IDE itself.

.

Sometimes when the sdk-tests project does not build correctly, try File > Invalidate Caches... and try restarting IntelliJ.

You should be able to set breakpoints and Debug the test directly from IntelliJ itself as seen from the above image.