Concerns about using UUID ID Generator - Discussion & Questions

Default UUID Generator in Camunda

The Camunda engine by default uses a UUID (Universally Unique Identifier) generator to create unique IDs for processes, cases, and other entities. Some users have expressed concerns about the use of this generator, specifically regarding its performance implications.

Performance Implications

Users have pointed out that the UUID generator can lead to slower database index performance due to the alphanumeric nature of the IDs generated. In comparison, numeric primary key IDs would be expected to provide better performance with indexing.

Database-centric ID Generation

Some users suggested that Camunda should use database-specific ID generation methods, such as database sequences or implicit sequencing, similar to how other databases manage primary keys.

Database ID Generation Comparison

UUID Generator vs. Database ID Generation

Database-aware Perspective

The database-centric approach appears to offer better performance compared to the UUID generator. However, it may require implementing a custom ID generator.

Key Considerations

• Implementing a Custom ID Generator: While this is an option, users should consider the complexities involved in implementing a custom ID generator.
• Potential Issues with Existing Instances: Those using Camunda in production might be concerned about the impacts of changing the ID generator strategy on existing live instances.