Secondary storage
Camunda uses a layered storage model that separates workflow execution data from data used by web applications and APIs.
About secondary storage
Secondary storage is one of the two complementary layers in Camunda’s data model:
| Layer | Purpose | Typical technologies |
|---|---|---|
| Primary storage | Persists real-time workflow execution state managed by Zeebe. | RocksDB (embedded in Zeebe) |
| Secondary storage | Stores workflow, decision, and task data for querying, visualization, and API access. | Elasticsearch / OpenSearch, RDBMS (H2, PostgreSQL, MariaDB) |
Secondary storage is not a duplicate of primary data. It represents the historical workflow and decision data generated by the engine, optimized for querying and visualization.
Supported storage options
Camunda supports the following secondary storage backends, depending on the version and use case:
| Database type | Availability | Use case |
|---|---|---|
| Elasticsearch / OpenSearch | General availability | Default for most production installations. |
| RDBMS (H2, PostgreSQL, MariaDB) | 8.9-alpha1+ | Lightweight local testing (H2) or future enterprise-grade RDBMS use. |
Data flow
The following diagram shows how secondary storage fits into the Camunda data flow.
- The Zeebe broker executes workflow instances and stores state in primary storage.
- The exporter, part of Zeebe, streams workflow and task data to secondary storage.
- Applications such as Operate, Tasklist, and the REST API read data from secondary storage.
Configure secondary storage
Learn how to configure secondary storage in Self-Managed environments using Helm, Docker, or manual deployment.
Although you should use secondary storage in nearly all your production environments, you can choose to disable secondary storage in limited scenarios, such as lightweight development environments, specialized technical use cases, or resource-constrained deployments. See run without secondary storage.
Manage secondary storage
Learn about best practices for data management, backups, and monitoring to ensure data integrity and performance.
Effective secondary storage management ensures stability, scalability, and data integrity across your Camunda environment. By following Camunda best practices, you can avoid data corruption, maintain compliance, and ensure your orchestration environment remains performant and reliable.