Task application architecture
A typical task application architecture consists of a task application frontend, a backend-for-frontend, and one or more data sources or services that contain business data relevant for the application users to perform their work. The backend implements Camunda Zeebe and Tasklist clients to retrieve and interact with tasks via Camunda APIs. For historical process instance data, Operate is also required.
Depending on the user task implementation type (job-based vs Zeebe user task) you use in your processes, you need to run either the Tasklist or Zeebe client to run operations on task. Task, form, and variable retrieval happens via the Tasklist API. Learn more about the differences of the task implementation types in the migration guide for Zeebe user tasks.
Starting a completely new project? Use only Zeebe user tasks to simplify your implementation.
Click on any element of this diagram to jump to the documentation page for the respective component:
Follow these resources to learn more about the individual components:
- Create a simple backend in the Tasklist API tutorial.
- Familiarize yourself with the Tasklist API for task, variable, and form retrieval, and to run operations on job-based user tasks.
- Learn how to use the Zeebe API to run operations on Zeebe-based user tasks.
- Understand how to design, embed, and customize forms.
- Understand how this architecture fits into the overall Camunda architecture with the Java greenfield stack.