I have not seen any blocks, glitches, or crashes. I have not heard anything about anyone having trouble with that type of thing. I think that the stability is pretty good.

The stability of the solution is good. We haven't had any problems in two years. There hasn't been any crashes or anything of that nature.

This is a reliable solution that depends on the Oracle database, which is a very well known and very trusted database around the world. It is considered to be the best database when compared to Microsoft SQL, IBM Db2, or Sybase HANA. 

The underlying infrastructure is very durable.

In terms of stability, once in a while, we encounter bugs. There is no perfect solution anywhere. What matters to us is the speed at which we get support. Yes, we have bugs. But when there are bugs and we raise a ticket, the speed at which this should be taken care of is what matters to us. So we have to subscribe to Oracle this year to be able to get that kind of software support, even if it is too expensive, and it is very expensive for us.

Some web 2.0 characteristics are unstable and can't be easily used, such as portals.

We have a lot of pain with instabilities and are not getting enough support from Oracle.

It can get slower under load.

I certainly encountered stability issues;

Not sure if they are exactly WebCenter related, but sometimes unknown exceptions were raised on runtime or deployment that could be resolved by restarting the server.

Regarding WSRP: Web Service for remote portlets feature generates metadata
files during deployment so that WSRP portlet can be used.

However, this leads to a situation where the application cannot be packaged and customized via deployment plan, rather it needs to be packaged during deployment.

The solution is stable.

There were performance issues.

In a cluster environment, we had stability issues with the satellite cache.