There are some problems and I don't think that this product is scalable. The product is supposed to be scalable but at this point, we are not in a situation where we can test it.

For scalability, it is basically the JVM. If you want to scale up, it is just a matter of adding a JVM. It can scale horizontally, and it can scale vertically. If you want to add 10 servers, just add a JVM. Right now, we have our own 14 instances.

We have a grid for JVM installations, so if we want to use the 10 servers, and other people also want to use them, they are likely to build something. It can be scalable.

I have not encountered any scalability issues.

No we did not.

We have not encountered any scalability issues on the cluster side, but we have seen problems with big messages on the .NET client.

No.

None, but there is a considerable important challenge with record versioning and serialization that needs upfront care decisioning.

We have encountered scalability issues. Currently, we have multiple clusters of six nodes each. At one point, we tried to scale to 12 nodes. We started to have a lot of nodes crashing, most probably because of all the node chatter.

No, the product supports clustering for different nodes (data, extend).

The scalability issue I encountered was that it costs a lot!

I have not encountered any scalability issues.

I think now I really need that more in a hardware way; but I would really not find that as a challenge anymore. We are actually able to do it more comfortably because now, whether I'm scaling up or scaling down, it's very transparent.

As mentioned, we have extended clusters between different sites, even though Oracle does not recommend this configuration.

Scalability was not an issue.

To add additional capacity, the cluster has to be fully recycled and that cause the down time of the environment.

I have not encountered any scalability issues either.

I have not encountered any scalability issues. In fact, we had a configuration that allowed the cache to fill up to its limit and then was flushed when entire cache was fully occupied.

I have not encountered any scalability issues.

No, from a product perspective.

Yes, from a license cost perspective.

Scalability is safe. The data is distributed/replicated. Adding/removing a node only has the cost of re-distributing the partitions of the data across the network.

There have not really been any scalability issues.

No.

We did not encounter any issues with scalability.