Top five things you need to know when sizing your Camunda Environment
In order to successfully operate Camunda, you need to take into account operation requirements when modeling business processes. You will want to use your existing tools and infrastructure for technical monitoring and alarming. This includes understand influencing aspects of performance and apply tuning strategies appropriately. As you size your environment for Camunda appropriately this will include provisioning sufficient Hardware/Compute and Database/Disk space.
What factors matter most with Camunda?
Unlike a lot of others, you don’t actually have to buy big hardware to size your Camunda environment. It really only hinges on two factors.
The container\application server you want to use
The amount of “Java working” your application has to do. Normally, this is your Delegation code.
How does all of that tie into your Compute?
Compute, not only Hardware, since Camunda can run in a container and ties directly to specific metrics that will map into demands you make on your system. This relates to factors such as:
Your Server Class(small, medium, large)
And your disk space
What are the top five things you need to know when sizing your Camunda Environment?
This podcast discusses 5 things you need to be aware of as “Best Practices” when sizing your Camunda Environment. Stuart and Max discuss the average duration between process starts, Average process run time, Wait States, Number of concurrent clients, and History Level.