On Joget Workflow Scalability
Since v3.0, we had done quite a number of code profiling steps and optimized the identified bottlenecks. There is significant performance improvement in v4. In terms of customer implementations, we have a customer in Asia that implemented a cluster of up to 5 servers on AWS (Amazon Web Services) to handle up to 1500 concurrent users. There's another in Europe that has several thousand total users running on a single on-premise server. As Joget Workflow is a platform and not directly an end-user app, the scalability and performance would depend on a number of factors e.g. complexity of the apps and use cases, usage patterns, tuning of the OS/DB/JVM/app server stack, etc. The best approach would be to perform profiling/sampling on specific apps/use cases that are considered slow, that would give a good indication on any possible bottlenecks/resource contention issues. There is a very general guideline at http://dev.joget.org/community/display/KBv4/ , but it is diff