Documentum is the most scalable product I have seen so far.

It is quite scalable because currently, around 6000 users are using it.

OpenText Documentum has been a pretty scalable product on-premises.

OpenText offers a wealth of service engines and components that can be seamlessly integrated with Documentum, enhancing its capabilities significantly. It has shown excellent versatility in supporting various databases, with Oracle being notably powerful in this regard. I would rate it eight out of ten.

For the volume and distribution model, it is quite scalable. Integration with other applications is less than IDR.

OpenText Documentum has amazing scalability. It's very flexible, and we can add more licenses whenever we need.

It is scalable. Particularly with the integration that OpenText now gives to the SAP and IBM Maximo systems through their XECM platform, it is definitely scalable. In the industries we work with, it works with the applications that people need to work with.

The product is scalable. 

The tool is scalable.

Documentum offers excellent scalability, even when deployed in Kubernetes, allowing for easy expansion as needed. Its robust object model ensures limitless scalability, a significant advantage for handling large volumes of data.

I rate the scalability a six out of ten because the bigger the project, the more complex it becomes. We have about five people in charge of maintenance.

In terms of scalability, Documentum is a very good product. It's scalable, flexible, and reliable. Our national card system has more than 30,000 users, of which about 6,000 are highly active.

Documentum is a highly scalable document management solution because it's built on a solid platform.

The product is very scalable. 

We are only using Documentum in-house, so there isn't a heavy usage. We have about 1,000 users in total, although there are only about 100 using it concurrently.

For our purposes, scalability has not been an issue.

The scalability is good.

No.

The core (content server and DFC) are reasonably well scalable. Several sub-products, like RMA and RPS, are really bad scalability-wise and many other aspects.

The content server could be more scalable if it didn't depend so much on dm_sysobject. The design overuses dm_sysobject without much need. Lightweight objects can be a way of solving this issue. Table partitioning can be useful also, but table partitioning can be a lot of work for solving a design problem.

It is easy to expand. We store many workflows in it and we are going to expand the project after the next upgrade to include all of our workflows. 

There are around 5,000 uses but after the upgrade, it will be closer to 20,000 users.

This solution is scalable, but for large scale implementations, we would always prefer Documentum, rather than SharePoint.

Currently, we have over 25,000 simultaneous users and the total users are more than 40,000.