Open Source Document Management System | OpenKM

Hi,

We have more than 1TB size of documents and no of documents will be millions, will the community version be able to handle this no or size of documents. We are not going to use OpenKM interface directly, we will have all our documents in OpenKM but use REST API services from another application to access the documents.

I read some old threads, moderator explains it should be optimized to handle large amount of documents, so if optimized community version will be able to handle these numbers (documents)?

Thanks!

Taking your words literally, "is optimized", the answers is, is not so optimized and tested as professional version. On professional version we have installation wit several millions of documents.

I do not know which is the biggest one on community. I know some user which have 100-200K documents. But we have not much information about for what are using community version and how many files are stored into.

The advantage you have is that you will not be using OpenKM UI. UI does a lot of things and is much probably you overload server from this scenario. Your scenario seems you want to have OpenKM as a container to being used by webservices. In this case the perfomance always will be better ( because UI features demands more hardware ). Obviously you must use MySQL, PostgreSQL etc... as database ( default HSQL is not recommended for production ).

Community will be enought to you ? I ignore, depends on a lot of things, concurrent users, what are you doing etc... ( take in mind rest need some miliseconds for each operation, if an operation needs 250ms and you need to do 10 times then 10x250 = 2500ms ( you need 2,5 seconds to complete operation ). I tell it because sometimes on the design of the connection is not taking on consideration the extra acumulated time for iterations, and depending the way you decided to solve the problem is more or less easy.

The good news are that always can promote your community to professional. But obviously for us is not much pleasant scenario, because if you have done some mistake on the way you decide the integration ( logic ) that will not be solved only promoting to professional probably will be need something else. Also take in mind the upgrades from one version to another needs some times. When we are talking about several milions of records, that means some process can be down for several hours until be completed.

Hi,

Thanks for detailed explanation, we are considering to move with MySQL.

We encourage moving to any database rather HSQL on production environment.