The solution is very scalable and that is the feature we like most. 

I rate scalability a nine out of ten. 

It offers excellent scalability capabilities, especially for organizations with several thousand users. It follows a centralized architecture rather than a distributed one.

It is a scalable solution. We have 2,000 customers and 35,000 end users of the solution. Also, we plan to increase the number of users.

We can cater the solution to every type of business. I rate the solution's scalability an eight-point four out of ten.

The product offers high scalability. There is a huge cost involved if I need to scale up.

Around 10 people in my company use the product.

The product is regularly used in my company and can be considered as the heart of the operations.

There is no need to increase the usage of the product because we mainly use the tool in our company to support the application. The people on my team can administer the database.

In-Memory's scalability is okay because it's focused on big databases. Scalability is a focus when used on a NoSQL database. When we use In-Memory in the Oracle database, which is an MDBMS, scalability is not a concern. The solution is only for enterprise-level customers.

Since we aren't using this as a SaaS, if we move to cloud, we can go for scalability easily. The on-premise solution is scalable. It's also good for cost reduction. If the client is looking for some cost reduction, it is not possible with the on-premise version, so it's better to go for SaaS or cloud.

There were 5000 Oracle Database In-Memory users in my previous company. I rate the product's scalability a ten out of ten.

In my experience, it scales quite well. Unfortunately, decent scale-out with RAC only works in Exadata, since Oracle relies on RDMA which is only available for InfiniBand.

I would rate the product's scalability a nine out of ten. 

From the scalability perspective, the concurrency that we expect is 2,000 users. We're only keeping only two years’ worth of data; not more than that. The data comes in and the old data actually goes out to the archives, and only the new data is there. The old data is an SAP, so we don't maintain that. For reporting purposes, we don't want them; we only maintain two years’ worth of data.

The only issues is with concurrency, and we tested it with 2,000 users, so it's fine.

This solution is easy to scale.

We have more than 50 Oracle Database In-Memory users in our organization. While occasional usage may increase, the technical infrastructure effectively manages these fluctuations. It demonstrates negligible impact on performance, even with incremental user growth. I rate the scalability a nine out of ten.

I'm not going to get into too much because I haven't tried that, I'll be honest. It offers quite a bit of scalability in terms of scaling out and scaling up because all of these features for pluggable databases and that’s the multitenant feature, but we also talked about the Database In-Memory feature, scale extremely well, especially in a real applications cluster or rack database environment. Container databases do take a little bit more thinking. You have a limited number, only 254 possible pluggable databases, inside a container database and you are essentially creating a different version of an Oracle database, container versus, as we call them, non-container or non-CDBs. When you're building that initial container database, you do have to think about which way am I going. The good news is there's a very simple procedure to take a non-CDB and make it into a PDB underneath a CDB with a very limited amount of downtime of the source non-CDB.

From the In-Memory side for 12.1.0.2 for setting up the In-Memory column store, it's literally change one initialization perimeter, bounce the instance, and you're ready to go. It's extremely simple to do that. There is also a really good tool that allows us to figure out which objects should be inside the In-Memory column store, called the In-Memory Advisor. That has even matured since about a year ago when that was first released, it's much easier to figure that type of thing out. In terms of implementation, it's really quick and almost painless, is what it comes down to.

The solution is scalable. Almost everyone in the company uses the solution.

It scales really well.

We had to scale it along with the rest of the ecosystem, not just this in particular, but the infrastructure as well. We had to scale both of them.

It scales well for our needs.

It scales to the needs of my customers.

The scalability is pretty decent. We've had clients that have scaled in the past, however, they didn't use Oracle to do so. That said, I believe it scales.

The scalability is good, of course. Oracle is known for its scalability.

The solution is scalable. 

The scalability of the solution is very good. It's able to support large amounts of data.

We don’t have any issues with scalability. It will meet our needs for the future.

It is scalable. 

Scalability is also very good.

We haven't needed to scale it yet in the two months we've been using it.