There are many factors involved in determining the server specifications needed to run Joget Workflow effectively. These are some of the non-conclusive factors:-
- Total number of users
- Maximum expected concurrent users
- Number of apps running on the platform
- Complexity of each of the apps
- Amount of data generated in each app
- Network infrastructure
For example, an environment with a small number of users running a heavily-used complex app might require more resources than an environment with large number of users running some simple apps only once a day.
So based only on number of maximum and concurrent users, you wouldn't be able to predict what is needed. Usually customers would start with a single application server first, and scale up or cluster when necessary.
Check out the following articles:-
- Joget Workflow Deployment Best Practices
- Joget Workflow Hardware Requirements
- Monitoring using VisualVM
- Joget Workflow Clustering and Performance Testing on Amazon Web Services (AWS)
It is not an easy task to provide exact hardware requirements without first knowing the complexity of the app, workflows, forms, etc. running on the Joget Workflow platform. However, we can propose an initial architecture for you to deploy, and you can scale accordingly as the traffic grows. Additionally, scaling can be done in many ways, e.g., application clustering, upgrade of hardware specs, add additional hardware servers, etc.
...
Also, please note that you will need to use the Joget Workflow Large Enterprise Edition (LEE) in order for you to be able to setup the clustered environment.
Please refer to this article for Deployment Best Practices.