Run your first Temporal application with the Java SDK
This tutorial is a work in progress. Some sections may be incomplete, out of date, or missing. We're working to update it.
- Level: ⭐ Temporal beginner
- Time: ⏱️ ~20 minutes
- Goals: 🙌
- Complete several runs of a Temporal Workflow application using the Temporal server and the Java SDK.
- Practice reviewing the state of the Workflow.
- Understand the inherent reliability of Workflow functions.
- Learn many of Temporal's core terminology and concepts.
Introduction
The Temporal server and a language specific SDK, in this case the Java SDK, provide a comprehensive solution to the complexities which arise from modern application development. You can think of Temporal as a sort of "cure all" for the pains you experience as a developer when trying to build reliable applications. Temporal provides reliability primitives right out of the box, such as seamless and fault tolerant application state tracking, automatic retries, timeouts, databases to track application states, rollbacks due to process failures, and more.
In this tutorial you'll run your first Temporal Workflow application and forever change the way you approach application development.
Prerequisites
Before starting this tutorial:
- Set up a local development environment for developing Temporal applications using the Java programming language
- Ensure you have Git installed to clone the project.
Project setup
This tutorial uses a fully working template application which can be downloaded as a zip or converted to a new repository in your own Github account and cloned. Github's "Creating a Repository from a Template" guide will walk you through the steps.
To use the Github project, execute these commands in a new Terminal window:
git clone https://github.com/temporalio/money-transfer-project-template-javacd money-transfer-project-template-java
To build the project, either open it with IntelliJ (the project will build automatically) or make sure you have Gradle installed and run the Gradle build command from the root of the project:
./gradlew build
Once your project has finished building, you are ready to go.
Application overview
This project template mimics a "money transfer" application that has a single Workflow function which orchestrates the execution of an Account object's withdraw() and deposit() methods, representing a transfer of money from one account to another. Temporal calls these particular methods Activity functions.
To run the application you will do the following:
- Send a signal to the Temporal server to start the money transfer. The Temporal server will then start tracking the progress of your Workflow function execution.
- Run a Worker. A Worker is a wrapper around your compiled Workflow and Activity code. A Worker's only job is to execute the Activity and Workflow functions and communicate the results back to the Temporal server.
Here's a high-level illustration of what's happening:
The Workflow function
The Workflow function is the application entry point. This is what our money transfer Workflow looks like:
src/main/java/moneytransferapp/MoneyTransferWorkflowImpl.java
public class MoneyTransferWorkflowImpl implements MoneyTransferWorkflow {
private static final String WITHDRAW = "Withdraw";
// RetryOptions specify how to automatically handle retries when Activities fail.
private final RetryOptions retryoptions = RetryOptions.newBuilder()
.setInitialInterval(Duration.ofSeconds(1))
.setMaximumInterval(Duration.ofSeconds(100))
.setBackoffCoefficient(2)
.setMaximumAttempts(500)
.build();
private final ActivityOptions defaultActivityOptions = ActivityOptions.newBuilder()
// Timeout options specify when to automatically timeout Activities if the process is taking too long.
.setStartToCloseTimeout(Duration.ofSeconds(5))
// Optionally provide customized RetryOptions.
// Temporal retries failures by default, this is simply an example.
.setRetryOptions(retryoptions)
.build();
// ActivityStubs enable calls to methods as if the Activity object is local, but actually perform an RPC.
private final Map<String, ActivityOptions> perActivityMethodOptions = new HashMap<String, ActivityOptions>(){{
put(WITHDRAW, ActivityOptions.newBuilder().setHeartbeatTimeout(Duration.ofSeconds(5)).build());
}};
private final AccountActivity account = Workflow.newActivityStub(AccountActivity.class, defaultActivityOptions, perActivityMethodOptions);
// The transfer method is the entry point to the Workflow.
// Activity method executions can be orchestrated here or from within other Activity methods.
@Override
public void transfer(String fromAccountId, String toAccountId, String referenceId, double amount) {
account.withdraw(fromAccountId, referenceId, amount);
account.deposit(toAccountId, referenceId, amount);
}
}
When you "start" a Workflow you are basically telling the Temporal server, "track the state of the Workflow with this function signature". Workers will execute the Workflow code below, piece by piece, relaying the execution events and results back to the server.
Initiate transfer
There are two ways to start a Workflow with Temporal, either via the SDK or via the CLI. For this tutorial we used the SDK to start the Workflow, which is how most Workflows get started in a live environment. The call to the Temporal server can be done synchronously or asynchronously. Here we do it asynchronously, so you will see the program run, tell you the transaction is processing, and exit.
src/main/java/moneytransferapp/InitiateMoneyTransfer.java
public class InitiateMoneyTransfer {
public static void main(String[] args) throws Exception {
// WorkflowServiceStubs is a gRPC stubs wrapper that talks to the local Docker instance of the Temporal server.
WorkflowServiceStubs service = WorkflowServiceStubs.newLocalServiceStubs();
WorkflowOptions options = WorkflowOptions.newBuilder()
.setTaskQueue(Shared.MONEY_TRANSFER_TASK_QUEUE)
// A WorkflowId prevents this it from having duplicate instances, remove it to duplicate.
.setWorkflowId("money-transfer-workflow")
.build();
// WorkflowClient can be used to start, signal, query, cancel, and terminate Workflows.
WorkflowClient client = WorkflowClient.newInstance(service);
// WorkflowStubs enable calls to methods as if the Workflow object is local, but actually perform an RPC.
MoneyTransferWorkflow workflow = client.newWorkflowStub(MoneyTransferWorkflow.class, options);
String referenceId = UUID.randomUUID().toString();
String fromAccount = "001-001";
String toAccount = "002-002";
double amount = 18.74;
// Asynchronous execution. This process will exit after making this call.
WorkflowExecution we = WorkflowClient.start(workflow::transfer, fromAccount, toAccount, referenceId, amount);
System.out.printf("\nTransfer of $%f from account %s to account %s is processing\n", amount, fromAccount, toAccount);
System.out.printf("\nWorkflowID: %s RunID: %s", we.getWorkflowId(), we.getRunId());
System.exit(0);
}
}
Make sure the Temporal cluster is running in a terminal.
If you are using Temporal CLI, start your server and specify a database filename. Temporal CLI uses an in-memory database by default, and that won't work for the demonstrations in this tutorial.
Start Temporal CLI with the following command:
temporal server start-dev --db-filename your_temporal.db --ui-port 8080
When you stop and start the server again, remember to specify the same database file each time.
Run the InitiateMoneyTransfer class within IntelliJ or from the project root using the following command:
./gradlew initiateTransfer
Next you'll explore one of the unique value propositions Temporal offers: application state visibility.
View the state of the Workflow with the Temporal Web UI
Temporal's Web UI lets you see details about the Workflow you're running. You can use this tool to see the results of Activities and Workflows, and also identify problems with your Workflow execution.
Visit the Temporal Web UI where you will see your Workflow listed.
Next, click the "Run Id" for your Workflow. Now we can see everything we want to know about the execution of the Workflow code we told the server to track, such as what parameter values it was given, timeout configurations, scheduled retries, number of attempts, stack traceable errors, and more.
It seems that our Workflow is "running", but why hasn't the Workflow and Activity code executed yet? Investigate by clicking on the Task Queue name to view active "Pollers" registered to handle these Tasks. The list will be empty. There are no Workers polling the Task Queue!
The Worker
It's time to start the Worker. A Worker is responsible for executing pieces of Workflow and Activity code.
- It can only execute code that has been registered to it.
- It knows which piece of code to execute from Tasks that it gets from the Task Queue.
- It only listens to the Task Queue that it is registered to.
After The Worker executes code, it returns the results back to the Temporal server. Note that the Worker listens to the same Task Queue that the Workflow and Activity tasks are sent to. This is called "Task routing", and is a built-in mechanism for load balancing.
src/main/java/moneytransferapp/MoneyTransferWorker.java
public class MoneyTransferWorker {
public static void main(String[] args) {
// WorkflowServiceStubs is a gRPC stubs wrapper that talks to the local Docker instance of the Temporal server.
WorkflowServiceStubs service = WorkflowServiceStubs.newLocalServiceStubs();
WorkflowClient client = WorkflowClient.newInstance(service);
// Worker factory is used to create Workers that poll specific Task Queues.
WorkerFactory factory = WorkerFactory.newInstance(client);
Worker worker = factory.newWorker(Shared.MONEY_TRANSFER_TASK_QUEUE);
// This Worker hosts both Workflow and Activity implementations.
// Workflows are stateful so a type is needed to create instances.
worker.registerWorkflowImplementationTypes(MoneyTransferWorkflowImpl.class);
// Activities are stateless and thread safe so a shared instance is used.
worker.registerActivitiesImplementations(new AccountActivityImpl());
// Start listening to the Task Queue.
factory.start();
}
}
Task Queues are defined by a simple string name.
src/main/java/moneytransferapp/Shared.java
public interface Shared {
static final String MONEY_TRANSFER_TASK_QUEUE = "MONEY_TRANSFER_TASK_QUEUE";
}
Run the TransferMoneyWorker class from IntelliJ, or run the following command from the project root in separate terminal:
./gradlew startWorker
When you start the Worker it begins polling the Task Queue. The first Task the Worker finds is the one that tells it to execute the Workflow function. The Worker communicates the event back to the server which then causes the server to send Activity Tasks to the Task Queue as well. The Worker then grabs each of the Activity Tasks in their respective order from the Task Queue and executes each of the corresponding Activities. You will get a console output showing that both activity tasks were executed by the Worker:
Withdrawing $18.740000 from account 001-001. ReferenceId: 2ab46ccb-3791-4dd2-84e6-62319eb710a2
Depositing $18.740000 into account 002-002. ReferenceId: 2ab46ccb-3791-4dd2-84e6-62319eb710a2
Congratulations, you just ran a Temporal Workflow application!
Failure simulation
So, you've just got a taste of one of Temporal's amazing value propositions: visibility into the Workflow and the status of the Workers executing the code. Let's explore another key value proposition, maintaining the state of a Workflow, even in the face of failures. To demonstrate this we will simulate some failures for our Workflow. Make sure your Worker is stopped before proceeding.
Recover from a server crash
Unlike many modern applications that require complex leader election processes and external databases to handle failure, Temporal automatically preserves the state of your Workflow even if the server is down. You can easily test this by following these steps (again, make sure your Worker is stopped so your Workflow doesn't finish):
- Start the Workflow again.
- Verify the Workflow is running in the UI.
- Shut down the Temporal server by either using 'Ctrl+C' or via the Docker dashboard.
- After the Temporal cluster has stopped, restart it. If you are using Temporal CLI, run the same command you used previously to ensure you use the same database file.
Visit the UI. Your Workflow is still listed.
Recover from an Activity error
Next let's simulate a bug in one of the Activity functions. Inside your project, open the AccountActivityImpl.java file and uncomment the line that throws an Exception in the deposit() method.
src/main/java/moneytransferapp/AccountActivityImpl.java
public class AccountActivityImpl implements AccountActivity {
@Override
public void withdraw(String accountId, String referenceId, double amount) {
System.out.printf(
"\nWithdrawing $%f from account %s. ReferenceId: %s\n",
amount, accountId, referenceId
);
}
@Override
public void deposit(String accountId, String referenceId, double amount) {
System.out.printf(
"\nDepositing $%f into account %s. ReferenceId: %s\n",
amount, accountId, referenceId
);
// Uncomment the following line to simulate an Activity error.
// throw new RuntimeException("simulated");
}
}
Save your changes and run the Worker. You will see the Worker complete the withdraw() Activity method, but throw the Exception when it attempts the deposit() Activity method. The important thing to note here is that the Worker keeps retrying the deposit() method.
You can view more information about what is happening in the UI. Click on the RunId of the Workflow. You will see the pending Activity listed there with details such as its state, the number of times it has been attempted, and the next scheduled attempt.
Traditionally application developers are forced to implement timeout and retry logic within the business code itself. With Temporal, one of the key value propositions is that timeout configurations (Schedule-To-Start Timeout, Schedule-To-Close Timeout, Start-To-Close Timeout, and Heartbeat Timeout) and Retry Policies are specified in the Workflow code as Activity options. In our Workflow code you can see that we have specified a setStartToCloseTimeout for our Activities, and set a retry policy that tells the server to retry them up to 500 times. But we did that as an example for this tutorial, as Temporal automatically uses a default retry policy if one isn't specified!
So, your Workflow is running, but only the withdraw() Activity method succeeded. In any other application, the whole process would likely have to be abandoned and rolled back. So, here is the last value proposition of this tutorial: With Temporal, we can debug the issue while the Workflow is running! Pretend that you found a potential fix for the issue; Re-comment the Exception in the AccountActivityImpl.java file and save your changes. How can we possibly update Workflow code that is already halfway complete? With Temporal, it is actually very simple: just restart the Worker!
On the next scheduled attempt, the Worker will pick up right where the Workflow was failing and successfully execute the newly compiled deposit() Activity method, completing the Workflow. Basically, you have just fixed a bug "on the fly" with out losing the state of the Workflow.
Conclusion
You now know how to run a Temporal Workflow and understand some of the key values Temporal offers.
Review
Answer the following questions to see if you remember some of the more important concepts from this tutorial:
What are four of Temporal's value propositions that you learned about in this tutorial?
- Temporal gives you full visibility in the state of your Workflow and code execution.
- Temporal maintains the state of your Workflow, even through server outages and errors.
- Temporal makes it easy to timeout and retry Activity code using options that exist outside of your business logic.
- Temporal enables you to perform "live debugging" of your business logic while the Workflow is running.
How do you pair up Workflow initiation with a Worker that executes it?
Use the same Task Queue.
What do you have to do if you make changes to Activity code for a Workflow that is running?
Restart the Worker.