As part of this commitment, we are excited to announce a significant evolution in our testing libraries: Camunda Process Test, designed specifically for Camunda 8.

Why the change?

Until now, Camunda 8 users have relied on the Zeebe Process Test (ZPT) library to unit test BPMN processes. ZPT served us well, leveraging an in-memory Zeebe engine with gRPC to run tests and verify process behavior.

However, as our platform evolved, ZPT could no longer fully support the latest Camunda 8 features, including our new REST API and user task functionalities. Additionally, as part of our API streamlining strategy, most of our gRPC endpoints will be phased out by version 8.10, making ZPT incompatible moving forward.

To address these challenges and provide our customers with enhanced testing capabilities, we’ve developed a completely new testing library: Camunda Process Test (CPT).

Introducing Camunda Process Test

The Camunda Process Test library is our next-generation testing framework, designed and built for our customers’ evolving needs. CPT offers powerful testing capabilities and fully aligns with the new Camunda 8 REST API, enabling comprehensive testing of BPMN processes, connectors, user tasks, and more.

Here are some highlights of what CPT offers:

• Improved developer experience: By leveraging technologies like TestContainers, CPT ensures faster test execution, simpler environment setup, and smoother integration into modern CI/CD workflows. Also, by using the in-memory H2 database as a secondary storage, the testing library keeps a small memory footprint.
• REST API integration: CPT fully integrates with the Camunda 8 REST API, providing extensive test coverage for the latest features, including Camunda user tasks, connectors, and advanced client commands.
• Enhanced assertions and test coverage: CPT provides a rich set of assertions and generates detailed test coverage reports after each test run. These enable developers to quickly pinpoint testing gaps and verify process behaviour more accurately.
• Automatic wait handling: CPT automatically manages process wait states, eliminating the need for manual waitForIdleState() or waitForBusyState() calls, significantly simplifying your test code.

Deprecation timeline for Zeebe Process Test (ZPT)

With the introduction of CPT in Camunda 8.8, we’re officially deprecating the Zeebe Process Test library. Here’s a clear timeline to help you plan your migration:

Camunda 8.8 (October 2025)

• Introduce CPT as the recommended testing library.
• Mark ZPT as deprecated (available but no longer actively enhanced).
• Provide a comprehensive migration guide and assertion mapping documentation.

Camunda 8.9 (April 2026)

• Transition: Both CPT and ZPT remain available and fully supported, allowing ample time for migration and testing.

Camunda 8.10 (October 2026)

• Fully remove Zeebe Process Test library from repositories and documentation.
• Customers must complete the migration to CPT before upgrading to 8.10.

Migration made simple

We understand that migrating to a new testing framework involves effort. To ensure a smooth transition, we’ll develop detailed resources, including:

• A comprehensive step-by-step migration guide from ZPT to CPT. It will include:
  • Clear mapping of existing ZPT assertions and utilities to their CPT counterparts
  • Practical example code snippets covering common migration scenarios
• Documentation featuring CPT’s new capabilities and best practices

These resources will be available together with the 8.8 release.

The migration involves the following steps:

1. Review existing test cases: Identify ZPT usage and custom assertions within your test suite.
2. Replace ZPT assertions with CPT equivalents: Use our assertion mapping guide for straightforward replacements.
3. Adapt to structural changes: Remove manual wait states and leverage CPT’s built-in automatic handling.
4. Migrate from Zeebe client to Camunda client: The Zeebe client is deprecated in favor of the Camunda client. CPT supports both clients until version 8.10.
5. Transition to TestContainers: Update local development environments and CI pipelines to use TestContainers, enabling consistent and fast test environments.
6. Utilize CPT’s enhanced capabilities: Leverage new test coverage reports, granular task lifecycle assertions, and improved connector testing.

Looking ahead

By transitioning to the Camunda Process Test, you’ll gain a more robust, flexible, and powerful testing framework aligned with the latest Camunda 8 features. While migration requires initial effort, the long-term benefits of improved test coverage, clearer assertions, and enhanced developer productivity are substantial.

We strongly encourage all customers to begin the migration process with the 8.8 release. Our documentation team and support resources will be ready to assist you in making this transition smoothly. Camunda documentation will provide detailed migration instructions and more information.

As always, we welcome your feedback and questions.

Happy testing!

The post Introducing Camunda Process Test—The Next Generation Testing Library appeared first on Camunda.

Simplified architecture for easy installation and getting started

Camunda 8.8 introduces a streamlined architecture that unifies core components—Zeebe, Operate, Tasklist, and Identity—into a single, production-ready distribution. By consolidating these components into a single deployable package, Camunda 8.8 reduces deployment complexity, simplifies resource configuration, and streamlines resource management. This approach makes installation and setup more straightforward, whether you’re preparing a production environment or just getting started with Camunda.

You can download the alpha release of the unified package as an executable Java application (Camunda Orchestration Core), available in our GitHub repository. For more information, we encourage you to watch this presentation from CamundaCon New York.

In earlier versions, each component of the Camunda Orchestration cluster—such as Zeebe, Tasklist, Operate, and Optimize—was deployed independently, either as separate deployments or within a StatefulSet (see Diagram 1). While Zeebe could support a fully distributed deployment model, components like Operate and Tasklist were often run as single instances. This previous approach added complexity, requiring individual scaling, configuration, and monitoring.

With Camunda 8.8, most components are merged into a single deployable package, available as a JAR file or Docker container. Optimize will continue to be deployed separately due to its architecture and importer requirements.

Camunda 8.8’s unified approach reduces the complexity of managing multiple independent services and minimizes the overhead involved. Additionally, the new exporter architecture (see Diagram 2) removes the need to deploy Operate, Tasklist, and Identity as separate services, further streamlining deployment.

This single deployable package simplifies resource configuration, management, and monitoring. For Kubernetes Helm deployments, starting from Camunda 8.8 alpha 1, Camunda Orchestration Core uses a single StatefulSet to run all components of the orchestration cluster. It consolidates computing resources into a single deployment, allowing for horizontal/vertical scaling while maintaining high availability (HA) and disaster recovery (DR) for all Camunda components. This approach reduces operational complexity, making it easier to manage and scale as needed.

The Identity component in Camunda 8.8 will also change how it is installed and configured:

• First, it will be integrated into a unified deployment package along with Zeebe, Tasklist, and Operate, streamlining deployment and reducing configuration complexity by bundling all major components together.
• Second, Identity will use Zeebe’s persistence storage instead of a PostgreSQL server, which enhances system consistency and reduces the need to manage additional databases.
• Third, Identity will be decoupled from Keycloak; while Keycloak is still supported, you can now use OpenID Connect (OIDC) to integrate directly with any compatible identity provider (IDP) of your choice. To learn more about the changes to the Identity component, please see the Identity blog post.

Upgrade Camunda 8.7 deployment to version 8.8

The upgrade path from version 8.7 to 8.8 is straightforward if you are using the recommended Camunda 8 deployment options—specifically, Helm Charts. Our charts will support the upgrade directly, simplifying the transition.

Additional upgrade considerations are necessary for deployments that use custom scripts, such as Docker containers, manual installations, or custom-developed Kubernetes deployments. In these cases, you can either continue to deploy with your original 8.7 topology and upgrade each component independently or adopt our Helm Chart approach for the upgrade, which allows for unifying the deployment into a single JAR or container executable.

With the 8.8 release, we’ll publish further guidance to help you upgrade from 8.7 to 8.8, providing detailed steps and best practices to ensure a smooth transition.

During the upgrade from Camunda 8.7 to 8.8 with Helm Charts, Zeebe will remain operational. However, minimal downtime may be required to migrate the Identity database. Operate and Tasklist may also require a brief downtime while these components are moved to a unified stateful set.

These interruptions are expected to be minimal. We recommend planning for this short downtime window to ensure that service disruptions are minimized and any impact is well managed.

Enhanced deployment options

Camunda 8.8 supports several deployment platforms, including Kubernetes (e.g., AWS EKS, Azure AKS, GKS, or OpenShift), manual installation (e.g., AWS EC2, VMWare VMs, etc.), container services (e.g., Docker Compose, AWS ECS, etc.), and local development using Camunda 8 Run or Kind.

Camunda 8.8 introduces a set of deployment reference architectures aimed at providing practical solutions for different deployment needs. These reference architectures are designed to help you understand and implement Camunda effectively based on your specific infrastructure requirements:

Kubernetes deployment with AWS EKS

This reference architecture outlines best practices for deploying Camunda on Amazon EKS. It covers infrastructure setup, resource scaling, and cluster management to ensure your Camunda environment is scalable and resilient. The architecture also provides guidance on integrating with other AWS services, such as AWS OpenSearch, AWS IAM, and HashiCorp Terraform.

Manual installation on AWS EC2

For organizations that do not use cloud-native platforms like Kubernetes or container services, this reference architecture provides guidance on implementing Camunda production clusters on AWS EC2 instances. It includes details on optimal instance sizing, network configurations, and security best practices to ensure robust performance and reliability.

While these provided reference architectures focus on specific platforms, we encourage you to use them as a foundation for deploying Camunda in their own unique environments or configurations. We plan to include detailed guides for Azure Kubernetes Service (AKS), OpenShift, and AWS container services in upcoming releases, providing more comprehensive deployment options for diverse infrastructures.

Kubernetes Helm Chart production deployment guide

With the 8.8 release, we plan to publish a new guide that explores the deployment of Camunda in Kubernetes. The guide will provide a detailed overview of the deployment process, including configuration options that enhance reliability, security, and scalability. It will also cover a variety of topics customers need to know to successfully deploy the Camunda Orchestration cluster in production.

Introducing Camunda 8 Run for pro developers

Camunda 8 Run, first released in version 8.6, is designed specifically for local development and testing, providing a lightweight setup without the need for a full-scale cluster. Camunda 8.8 will enhance C8Run to better meet the needs of professional developers:

• Local development and testing: Camunda 8 Run offers an easy way to run Camunda on a local machine, making it perfect for development and experimentation. It eliminates the need for a complex setup or a full Kubernetes cluster, allowing developers to get started quickly and focus on building and testing workflows.
• Integrated components: Camunda 8 Core Orchestration Cluster includes essential components like Zeebe, Operate, Tasklist and now Identity in one package. This integration ensures a seamless developer experience by providing all core functionalities needed for process automation in a single environment.
• Enhanced developer experience: By streamlining setup and bundling all necessary tools, C8Run helps developers iterate quickly, test new features, and validate workflows without the overhead of managing a distributed deployment.

Ideal use cases for Camunda 8 Run

Camunda 8 Run is perfect for local development and testing scenarios. It provides a lightweight setup that is easy to configure, making it an excellent choice for developers who need a fast and simple environment to build and experiment with process automation. Camunda 8 Run allows for efficient workflow testing without the complexity of managing high availability, failover, or scaling concerns, which are typically needed in production environments.

More sophisticated platforms—like Kubernetes or infrastructure as service (IaC) systems such as ArgoCD, Ansible, or Terraform—are recommended for production-grade deployments requiring advanced capabilities (e.g., high availability, enterprise-level security, and resilience). This makes Camunda 8 Run an optimal solution for rapid prototyping and local experimentation and for smoothly transitioning to full-scale production deployments using Camunda Orchestration Core.

Frequently asked questions about deployment in Camunda 8.8

What are the main differences between Camunda 8.7 and 8.8? 

Among other changes, Camunda 8.8 introduces a streamlined architecture, consolidating core components like Zeebe, Operate, and Tasklist into a single deployable unit, simplifying deployment and management.

It also provides enhanced deployment options such as new Kubernetes Helm guides, deployment reference architectures, and improved support for professional developers through Camunda 8 Run.

Can I use Camunda 8 Run for production environments?

Camunda 8 Run is primarily designed for local development and testing, providing a lightweight and easy-to-set-up environment. However, for those interested in running Camunda as a single deployable unit in production, we will soon publish a detailed guide on how to deploy the unified Jar file in a production setting.

This guide will provide the right way to leverage the benefits of a new architecture (such as simplicity of installation, as in the case of Camunda 8 Run) while ensuring scalability, high availability, and enterprise-grade security for production environments.

What deployment options are available for Camunda 8.8?

Camunda 8.8 can be deployed using Kubernetes with Helm Charts (e.g., AWS EKS, Azure AKS, or OpenShift), manually using a JAR on a VM or any other infrastructure platform, Docker Image (e.g., Docker-Compose or AWS ECS), or using C8Run, Docker-compose, or Kind for local development.

Will there be any downtime when upgrading from Camunda 8.7 to 8.8?

Zeebe might experience minimal downtime as it migrates Identity data into a new schema. Operate and Tasklist may experience small downtime while their pods are restarted with the new version. We recommend planning for this small window of potential downtime. More details will be outlined in the update guide published on the release date of Camunda 8.8.

The post Streamlined Deployment with Camunda 8.8 appeared first on Camunda.

In short, Camunda 8.8 brings these key changes to identity management:

• Cluster-level identity management
• Decoupling from Keycloak
• New resource-based permissions
• Enhanced REST API endpoints

These architectural adjustments in Camunda 8.8 offer several clear benefits:

• Flexibility: Camunda 8.8 will offer limited built-in user management functionality, eliminating the need to run Keycloak. Users requiring a more feature-rich identity provider can seamlessly integrate their own identity provider (IdP) through OpenID Connect (OIDC).
• Enhanced control: With identity and user groups managed within each cluster, organizations gain more precise control over user access.
• Security: The principle of least privilege ensures that access is tightly controlled, reducing the risk of unauthorized actions.
• Granularity: Resource-level permissions provide a level of customization that enables you to fine-tune access at every level.

Key changes in Camunda 8.8 Self-Managed

Camunda 8.8 introduces significant advancements to streamline installation, configuration, identity management, and REST API capabilities, further enhancing user flexibility and control.

Removing Keycloak

A notable change is the removal of the built-in Keycloak integration, which grants users more freedom in selecting their preferred IdP. While Keycloak is still fully supported as an external option, Camunda 8.8 enables users to integrate any compatible IdP, providing greater customization and alignment with organizational standards. OIDC remains the standard for seamless integration with chosen providers.

No requirement for relational database

Beyond rethinking identity management, Camunda 8.8 simplifies installation by removing the requirement for a relational database in single orchestration clusters, reducing complexity and making the setup more user-friendly. Identity settings are now configured at the orchestration cluster level, allowing each cluster to have unique OIDC configurations.

This cluster-specific setup empowers organizations to assign different IdPs across clusters, offering improved control over permissions and user group mappings, resulting in a more streamlined and efficient configuration experience.

New identity-focused endpoints

Camunda 8.8 introduces new identity-focused endpoints within the Camunda 8 REST API, providing enhanced query capabilities for managing process entities, such as processes, decisions, user tasks, and forms. This marks the beginning of a shift from component-specific APIs (like Tasklist and Operate) to unified, centralized queries.

The Camunda 8 REST API endpoints enable managing users and permissions within orchestration clusters, supporting resource-based authorizations for fine-grained access control. This approach strengthens control over resource access, building a secure, scalable foundation for customizable workflows across various organizational needs.

Embracing the principle of least privilege

Camunda 8.8 also introduces a stricter adherence to the principle of least privilege, a core security practice. When authorization is enabled, users do not have default access to applications like Tasklist and Operate, or to any resources. Permissions must be explicitly granted, ensuring that users only have access to what is necessary.

We’re also introducing resource-level permissions, applying to process definitions and web applications. Admin users will continue to have full access, but regular users will need to be granted specific permissions to perform actions or view resources. For organizations that build custom frontends and access Camunda via API, users with API permissions can still access process data through the API.

Managing identity in SaaS

For our SaaS customers, identity management in Camunda 8.8 remains consistent with Camunda 8.7, allowing the attachment of a single IdP per organization. However, we are extending cluster-level identity capabilities to SaaS as well. This means that user groups, roles, and access permissions can now be managed at the cluster level, giving SaaS customers the same granular access control as in Self-Managed environments.

Elevating identity management

Camunda 8.8 marks a major step forward in our Identity service. By moving to a more flexible architecture and offering deeper control at the cluster level, we’re enabling our users to better manage their identity and access needs. Whether you’re in a Self-Managed environment or utilizing our SaaS offering, the upcoming release ensures a smoother, more secure experience for all users.

Stay tuned for the official release, and get ready to take advantage of these new features!

The post Introducing Enhanced Identity Management in Camunda 8.8 appeared first on Camunda.

Camunda 8 background

Camunda 8 represents an evolution in process orchestration—designed to help businesses realize value today while enabling the enterprise architecture needed to support what comes next. Camunda 8 continues our history of embracing open standards and uniquely composable architecture to orchestrate and automate end-to-end business processes without compromise, but adds support for massive horizontal scale, improved collaboration between the business and IT, enhanced connectivity, and intelligence throughout, from co-pilots to the orchestration of AI, to building and deploying agents.

Camunda 7 Enterprise Edition End of Life—key dates

Today, we announce the extension of the Camunda 7 Enterprise Edition EoL from April 2027 to April 2030. The new EoL dates are:

• New EoL Date: April 9, 2030.
• Minor Releases: Final feature release (7.24) scheduled for October 14, 2025 (no changes).
• Ongoing Patches & Support: Security patches and support are included as part of your subscription fees until April 2030.
• Extended Support Option: Available for an additional fee from April 2030 through April 2032 (previously April 2030).

What this means for you

With this extension, customers on Camunda 7 Enterprise Edition will continue to receive security patches and support until the new EoL date, allowing them more flexibility to prepare for migration.

While we are extending the EoL, we highly recommend customers use this time to understand and plan their migration efforts:

• Leverage the many resources available to you and start discussing migration now by reaching out to your Customer Success Manager, Technical Account Manager (if applicable), our Consulting team, and your partner, etc.
• Explore the resources linked below for on-demand support and insights. 
• Review the Camunda 8 feature roadmap (and work directly with the Camunda team) to determine an appropriate timeline for your migration.
• Plan and budget your migration project so that you are ready to execute once your targeted Camunda 8 version is available.

Camunda 7 Community End of Life

The EoL date for Camunda 7 Community Edition has not changed. Please note that the final feature release for Camunda 7 (7.24) is still scheduled for October 14, 2025, and the repository will be archived shortly after. After this date, no further releases, including security patches, will be made for Camunda 7 Community Edition. If you need continued support for your solutions running on Camunda 7 Community Edition beyond that date, contact Camunda to explore an Enterprise license and take advantage of extended support timelines.

Resources

• Learn about the Camunda 8 feature roadmap.
• Check out our migration guide. Leave feedback via our forum.
• Review our recent blog post regarding migration strategy.

Camunda remains committed to removing migration blockers between Camunda 7 and Camunda 8. As Camunda continues to innovate and push the boundaries of process orchestration and automation, we are more committed than ever to empowering your organization’s success every step of the way!

If you have any questions or need guidance on migration planning, please contact your Customer Success Manager, the CSM team, or your Technical Account Manager (if applicable).

The post Camunda 7 Enterprise End of Life (EoL) Extension Announcement appeared first on Camunda.

There is so much we’re excited to share and learn about all the innovation in the process orchestration and automation space this May in Amsterdam.

Where and when is CamundaCon 2025 Amsterdam?

You can join this conference in person at the beautiful Beurs van Berlage, Damrak 243, 1012 ZJ, Amsterdam, Netherlands, on May 14–15, 2025.

We’ve got an incredible experience lined up at the venue this year, but for our global audience, we will have an online-only version as well for virtual attendees.

You can register now for either option right here.

What’s on the agenda?

The full agenda is live right here, so be sure to check it out! We’ve pulled out a few highlights for you below to give you just a taste.

Speakers

As always, the agenda is packed with curated sessions, featuring multiple tracks so you can choose what interests you the most. You’ll hear from industry leaders at globally recognized organizations such as Swisscom, T-Systems, Rabobank, BT Group, HSBC, and more. You’ll also hear directly from the leadership team at Camunda, along with many of the Camundi who are designing and developing the future of process orchestration and automation every day.

Industry tables

At these industry tables (in-person only), you’ll have an opportunity to connect with fellow Camunda users in your industry as well as Camunda professionals, and engage in conversations tailored to industry-specific needs.

Masterclasses

For our in-person attendees, we’re offering a selection of three hands-on masterclasses. These are limited to a certain number of seats and already selling out, so don’t miss your chance! Dig deep into one of these three topics:

• AI orchestration, where you’ll master the art of coordinating AI agents and other AI technologies.
• SAP enablement, where you’ll learn all about Camunda’s SAP integration and how Camunda’s orchestration capabilities can enhance SAP.
• Build your own migration strategy, where you’ll learn about the value you can unlock in Camunda 8, the technical implications of migrating from Camunda 7 to Camunda 8, as well as common migration approaches so you map out your own journey.

Executive meetings

Meet with Camunda leaders like CEO Jakob Freund, CTO Daniel Meyer, or cofounder and chief technologist Bernd Ruecker for 1:1 conversations. These are available on both day 1 and day 2 of the conference. Reach out to your Camunda contact today to get your meeting scheduled.

Hackday

Come and get your hands dirty by building something new! In this hackday, you’ll collaborate in teams to craft exciting and engaging projects using Camunda. There will be two distinct challenges tailored for tech-savvy individuals as well as for visionary BPMN business enthusiasts. Be sure to sign up during registration for this in-person event, as seats are limited.

Unconference

A staple of Camunda Community events, this is a much-loved participant-driven event that is open to all in-person attendees. Collaborate with other attendees to drive the agenda, discuss a range of technical and business topics, and learn from other experts.

Aftershow party and networking

After wrapping up a busy first day of the conference, don’t forget about the afterparty! With music, food and drink, this is a lively and fun chance to relax and connect with other attendees.

How do I join?

So glad you asked! You can register for the event by clicking the button below. And be sure to bring your friends and colleagues, because groups of five and larger get 20% off right now. We can’t wait to see you there!

The post CamundaCon 2025 Amsterdam: What You Need to Know appeared first on Camunda.

Our web applications have historically used importers and archivers to consume, aggregate, and archive historical data provided by our Elasticsearch (ES) or OpenSearch (OS) Exporter.

In the past year, we’ve engineered a new Camunda Exporter, which brings the importer and archiving logic of web components (Tasklist and Operate) closer to our distributed platform (Zeebe). This allows us to simplify our installation, enable scalability for web apps, reduce the latency to show runtime and historical data, and reduce data duplication (resource consumption).

In this blog post, we want to share more details about this project and the related architecture changes.

Challenges with the current architecture

Before we introduce the Camunda Exporter, we want to go into more detail about the challenges with the current Camunda 8 architecture.

When a user sends a command to the Zeebe cluster (1), it is acknowledged (2) and processed by the Zeebe engine. The engine will confirm the processing with an event.

The engine has its own primary data store for runtime data. The primary data store is optimized for low-latency local access. It contains the execution state that allows the engine to execute process instances and move its data along in their corresponding processes.

Our users need a way to search and visualize process data (running and historical data), so Camunda 8 makes use of Elasticsearch or OpenSearch (RDBMS in the future) as secondary storage. It allows the separation of concerns between runtime data for process execution and history data for querying.

Camunda’s exporters are a bridge between primary and secondary data stores. The exporters allow the Zeebe system to stream out data (events) (3). Within the Camunda 8 architecture, we support both the ES and OS exporters. For more information about this concept and supported exporters, please visit our documentation.

The exported data is stored in what we unofficially refer to as Zeebe indices inside ES or OS. Web applications like Tasklist and Operate make use of importers and archivers to read data from Zeebe indices (4), aggregate, and write them back into their indices (5). Based on these indices, users can query and search process data (6).

Performance

Customers have reported performance issues, which are inherited with this architecture. For example, the delay of data shown in Operate can range from around five seconds to, in the worst scenarios, minutes or hours.

The time is spent in processing, exporting, flushing, importing, and flushing again, before the users see any data change. For more detailed information, you can also take a look at this blog post.

This means the user is never able to follow a process instance in real time. But there is a general expectation that it is at least close to real time, meaning that it should at max take 1-2 seconds to show updates.

Reducing such latency and improving the general throughput needs a general architecture change.

Scalability

What we can see in our architecture above is that when we scale Zeebe clusters and partitions or set them up for large workloads, the web applications do not scale automatically with it, as they are not directly coupled.

This means additional effort to make sure the web applications can handle certain loads. The current architecture limits the general scalability of the web applications, due to the decoupling of exporter-importer and no real partitioning of data in the secondary storage.

We want to make the web application more scalable to handle changing processing workloads.

Installation complexity

You can run the different components of the Camunda platform separately, e.g. separate deployments for Zeebe, Tasklist, Operate, etc. This gives you a lot of flexibility and allows for massive scale. But at the same time, this makes the installation harder to do—even with the help of Helm charts.

We want to support a simpler installation as an alternative. That wasn’t possible in this architecture because of a missing single application and the need for separate components.

Data duplication and resource consumption

Web applications like Operate and Tasklist have historically been grown and developed separately. As we have seen, they could have been deployed separately as well.

This was also why they had separate schemas. Tasklist used a subset of Operate schema but added additional necessary indices to store information about user tasks, etc. When deploying both applications, this caused an unnecessary duplication of data in ES or OS.

As a consequence of this, we are consuming more disk space than necessary. Furthermore, ES/OS has a higher load on indexing new data than should be necessary.

We want to reduce this to minimize the memory and disk footprint needed to run Camunda.

One exporter to rule them all

Understanding those challenges, we rearchitected our platform to get rid of the aforementioned challenges. In the new architecture, we have built a Camunda exporter to replace the exporter/importer from the old architecture.

The Camunda Exporter brings the importer and archiving logic of web components (Tasklist and Operate) closer to the distributed platform (Zeebe).

The exporter consumes Zeebe records, aggregates data, and stores the related data into shared and harmonized indices that are used by both web applications. Archiving of data is done in the background, coupled with the exporter but not blocking the exporter’s progress.

Introducing this Camunda Exporter allows it to scale with Zeebe partitions and simplifies the installation, as importer and archiver deployments will be removed in the future.

The architecture diagram above is a simplified version of the actual work we have done. It shows an installation for a greenfield and a new cluster (no previous data).

More complex is a brownfield installation as shown in the diagram below, where data already exists.

We were able to harmonize the existing index schema used by Tasklist and Operate, reducing data duplication and resource consumption. Several indices can now be used by both applications without a need to duplicate the data.

With this new index structure, there is no need for additional Zeebe indices anymore.

Note: With 8.8, we likely will still have the importer/exporter (including Zeebe indices) to make use of Optimize (if enabled), but we aim to change that in the future as well.

Migration (brownfield installation)

Brownfield scenarios, where the data already exists and processes are running in an old architecture, are much more complex than greenfield installations. We have covered this in our solution design and want to briefly talk about it in this blog post. A more detailed update guide will follow with the Camunda 8.8 release.

When you update to the new Camunda version, there will be no additional effort for the user regarding data migration. We are providing an additional migration application that takes care of enhancing process data (in Operate indices) which can be used by Tasklist. Other than that, all existing Operate indices Operate can be used by Tasklist.

Reducing the installation complexity is a slower process for brownfield installations. Importers still need to be executed to drain the preexisting data in indices created by ES or OS exporters.

After all older data (produced before the update) is consumed and aggregated, importers and exporters can be turned off as well but can also be kept for simplicity. The importers will communicate via metrics if they are done and by writing to a special ES/OS index. More details will be provided in the following update guide.

Conclusion

The new Camunda Exporter helps us achieve a more streamlined architecture, better performance, and stability (especially concerning ES/OS). The target release for the Camunda Exporter project is the 8.8 release.

To recap the highlights of the new Camunda Exporter, we can:

1. Scale with Zeebe partitions, as exporters are part of partitions. The data injection and the data archiving scales inherently.
2. Reduce resource consumption with harmonized schema. Data is not unnecessarily duplicated between web applications. ES and OS are not unnecessarily overloaded with index requests for duplicated data.
3. Improve performance, due to reducing additional hop. As we do not need to wait for ES/OS to flush twice and make data available, we can reduce one flush interval from our equation. We don’t need to import the data and store it in Zeebe indices, so we shorten the data pipeline. This was shown in one of our recent chaos days but needs to be further investigated and benchmarked, especially with higher load scenarios.
4. Simplify installation by bringing business logic closer to the Zeebe system. We no longer need separate applications or components for importing and archiving data. It can be easily enabled within the Zeebe brokers. The Camunda Exporter has everything built in.

I hope this was insightful and helpful to understand what we are working on and what we want to achieve with the newest Camunda Exporter. Stay tuned for more information about benchmarks and other updates.

Join us at CamundaCon to learn more

Looking to learn more about this new architecture and how the Camunda Exporter will help you? I’ll be giving a talk on the new Camunda Exporter at CamundaCon Amsterdam in May. Join us there in person to catch the session and so much more.

The post One Exporter to Rule Them All: Exploring Camunda Exporter appeared first on Camunda.

Choosing your preferred cloud provider for your Camunda SaaS account helps ensure:

• A solid fit with your enterprise cloud strategy, including security policies and compliance requirements
• Easier integration with workloads that are already running on a particular cloud provider
• Increased flexibility to choose where business process data is stored so you can satisfy data residency requirements
• Opportunities to optimize performance through access to more geographic regions

Take advantage of expanded region support

We know that the ability to specify the region where Camunda clusters run is important to many of our customers. All Camunda SaaS customers can choose from a wide variety of regions, including AWS’s Frankfurt (europe-west2) and Virginia (us-east-1) regions.

Purchase Camunda on AWS Marketplace

Camunda is available for purchase on AWS Marketplace so you can get started fast, whether you’re interested in a free trial or you’re ready to migrate processes to the cloud. If you’re a current Camunda customer and you’re interested in SaaS, please contact your customer success manager.

The post All Camunda 8 SaaS Editions Now Available on AWS appeared first on Camunda.

While we initially aimed to release this streamlined architecture in early 2025, internal testing and release hardening have revealed the need for additional time to ensure we meet our high standards for quality and seamless migration. As a result, we have decided to take two actions: postpone our 8.7 release to April, and move the architecture streamlining scope to the 8.8 release in October 2025.

The focus of the upcoming April 8.7 release will be on task automation capabilities:

• Robotic Process Automation (RPA): With release 8.7, Camunda is excited to offer our initial release of RPA which allows organizations to embed RPA directly into comprehensive end-to-end processes using Camunda’s composable architecture. You can seamlessly integrate existing RPA bots or new bots developed with our RPA services, all within the same platform.
• Intelligent Document Processing (IDP) based on Document Handling: As you may have seen in the 8.6 alpha, Camunda now supports document handling. With 8.7, we will provide more functionality with additional support document functions for upload, download and delete for various storage platforms.
  
  This document handling functionality provides the foundation for our intelligent document processing (IDP), which will allow you to automate and simplify how complex documents are handled, reducing manual errors and operational costs. With features to extract document data using AI and LLM, you will have visibility into the documents in your process gaining insight into both structured and unstructured documents identifying patterns and trends promoting strategic decision-making.
• Ad-hoc subprocess powered AI Agents: Our 8.7 release also provides an introduction to AI Agents via ad-hoc subprocesses. Taking advantage of this BPMN standard, these AI agents reparent a task or collection of tasks that can exist for handling a specific case or cases. Tasks within these ad-hoc processes can be executed in any order, executed several times, or skipped. The execution of these tasks is decided by AI.
  
  The ad-hoc subprocess was originally added to the standard to allow for dynamic task interaction—letting users decide which task within the scope can be activated. We’ve innovated on this idea by using this BPMN feature to give AI Agents control over the actions they can perform during a part of the process.
• SAP Integration: Finally, 8.7 includes Camunda integration with SAP. Camunda’s integration with SAP allows organizations to integrate both SAP and non-SAP systems into a single end-to-end process providing visibility and standard adherence. With OData and RFC connectors, you can seamlessly integrate both SAP S/4HANA and SAP ECC environments. Camunda also offers BTP integration so SAP customers can render Camunda forms directly in their SAP Fiori tasks.
  
  This integration provides the technical foundation to ensure seamless, standardized integrations and smooth operations across your SAP tech stack.

The 8.8 release, coming in October 2025, will ship the streamlined architecture, with improvements in the core:

• Improved developer experience
  • Unified REST API for former Zeebe, Operate, Tasklist, Identity APIs
  • Advanced Search Query API as part of Unified REST API
  • Updated Camunda Java SDK and Spring SDK
    
• Faster production installation and simplified High Availability-Deployments
  • Orchestration Cluster: All-in-one distribution of the core orchestration components
  • New Camunda Exporter: Improved data pipeline, simplified HA-Deployments and unified data schema for Operate and Tasklist components
  • Rearchitected Identity Management (cluster-specific permissions management and removed keycloak dependency)

Our 8.7 release is packed with new task-based capabilities and innovative AI features, and 8.8 will deliver on a streamlined architecture for a substantially improved developer experience. We appreciate your patience and understanding as we continue to provide the highest-quality releases in the upcoming months.

The post Camunda 8.7 and 8.8 Release Update appeared first on Camunda.

Choosing the cloud provider for your Camunda SaaS installation enables you to:

• Gain flexibility for your process orchestration and automation implementation at no extra cost.
• Ensure you comply with your organization’s public cloud policies and more easily procure Camunda by choosing an approved cloud provider.
• Reduce latency and optimize process performance through access to more geographic regions.

Sign up for a free trial today

Whether you’re a new Camunda user or an experienced customer, you can sign up for a free trial of Camunda 8 and select AWS. If you have questions about your Camunda trial, visit our community forum.

The post Announcing Camunda 8 SaaS Free Trials on AWS appeared first on Camunda.

Since the launch of Camunda Enterprise on the AWS Marketplace, our alignment with AWS has gone from strength to strength, guided by the expertise of our AWS Partner Development Manager and Account Manager. The journey has been marked by noteworthy achievements and participation in key AWS events, including AWS Summits in London, Berlin, New York City, and Zurich, as well as the AWS Marketplace Conference in Bellevue, and the inaugural AWS Startup Summit in San Francisco. Our 2024 engagement with AWS isn’t over yet either, continuing with Camunda executives attending AWS re:Invent in Las Vegas, December 2-6, where customers can meet with our team.

Our collaboration in 2024 has yielded remarkable results:

• Significant revenue has been driven through co-sell activities and marketplace transactions.
• Over 75 co-sell opportunities are being worked in the APN Customer Engagements (ACE).
• Camunda’s presence at AWS events has expanded our reach and solidified our partnership.

These efforts culminated in October with Camunda achieving the prestigious ISV Accelerate status in the AWS Partner Program, an endorsement of our commitment to providing solutions that seamlessly integrate with AWS services.

Looking forward, we are eager to introduce new initiatives that further leverage AWS capabilities, such as:

• The imminent launch of Camunda Intelligent Document Processing, which can significantly reduce manual errors and operational costs when businesses handle and process complex documents. This solution leverages AWS Textract and Comprehend capabilities and contributes to Camunda’s composable architecture.
• The collaboration with the Generative AI Innovation Center for the integration of AWS Bedrock services into our BPMN modeler, optimizing operational efficiency and enhancing user experience with Camunda Copilot.
• The upcoming release of Camunda SaaS on AWS, which will provide users with unparalleled scalability and ease of use.

As we prepare for AWS re:Invent, we reflect on a year marked by growth and look forward to continuing our strong partnership with AWS in 2025. This is just the beginning of an even more innovative and successful collaboration.

Stay tuned for more updates as we continue to evolve and excel in the AWS ecosystem. Ever onward!

The post Camunda Achieves ISV Accelerate Status with AWS appeared first on Camunda.