1
0
-1
1 answer
- 10-1
Hi Stephanie,
With regards to your questions, please see below.
1. For example, how many requests/new processes does your joget instance handle on a monthly or yearly basis? How many users do you have active?
- There is no definite answer to this question. Please see item 3 below.
2. And has anyone had success getting LDAP connected in the community edition?
- The Community Edition does not come with LDAP support. You would have to use the Enterprise Edition to connect to LDAP or develop a custom Directory Manager plugin to handle LDAP connections.
- Joget allows pluggable Directory Manager implementations to cater to different authentication and authorization requirements. In the Enterprise Edition, a Security Enhanced Directory Manager and LDAP Directory Manager are provided by default.
- So far, I am not sure if others have develop a LDAP plugin for the Community Edition or not.
3. We are planning on having at least 2000 requests per month, with about ~200 users active in the system at once, maybe 20,000 users total (but probably only 1000 "regular" users who log in on a regular basis). Is that something the community or enterprise edition could handle without becoming sluggish or crashing?
- As Joget 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 we would suggest is 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/Joget+Workflow+Hardware+Requirements, but it is difficult to recommend specific environments. From what we know, each of our customers have very varied infrastructures to support different requirements because there are are potentially many factors involved, for example:
- 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
- etc.
For the standard Enterprise Edition/Community Edition, you can perform vertical scaling by increasing server resources as required when load increases. If there are bottlenecks it is important that the deployment is tuned and optimized e.g. Java VM tuning, app server tuning, database optimization, etc. There's an article in the Knowledge Base for this http://dev.joget.org/community/display/KBv4/Joget+Workflow+Deployment+Best+PracticesIf a single node is not enough, then horizontal scaling can be done by clustering and load-balancing multiple copies of Joget on separate application servers. There is a clustering guide document (http://dev.joget.org/community/pages/viewpage.action?pageId=12977334), but clustering is only available in the Large Enterprise Edition.Thanks and cheers.JackAdd your comment...
I was wondering how large other users systems got?
For example, how many requests / new processes does your joget instance handle on a monthly or yearly basis? How many users do you have active?
And has anyone had success getting LDAP connected in the community edition?
We are planning on having at least 2000 requests per month, with about ~200 users active in the system at once, maybe 20,000 users total (but probably only 1000 "regular" users who log in on a regular basis). Is that something the community or enterprise edition could handle without becoming sluggish or crashing?