Adobe Experience Manager is quite a stable solution.

Adobe Experience Manager is a stable solution. It's high-performing and it's better than other CMS tools in the market. Adobe Experience Manager has a quick response time, so within seconds, the server is able to respond to the web browser. In terms of security, the solution is also very secure.

It is a stable solution.

The cloud version is somewhat stable, but not all of the features are supported yet.

I rate Adobe Experience Manager an eight out of ten for stability.

So far, the stability has been good. Since Adobe Experience Manager has the multiple publisher concept, if any one of the servers goes down because of the traffic load, you can easily spin up a new server.

It's stable. From my understanding, especially with AEM as a Cloud Service, they've resolved those issues. When we were on AEM on-premises, if there was a bug, they'd do service pack installations to fix them. 

Now, since they're on AEM as a Cloud Service, Adobe just releases a new version, and it automatically upgrades in AEM Cloud.

Overall, there were no stability issues; I have found bugs and workarounds, like on any other platform.

Rarely.

AEM, when setup using Mongo, rapidly gains size. Hence it consumes a lot of storage space in a very short period of time.

Memory leaks - yes that really impacts overall stability. Actually, it is the problem of zombie OSGi services.

We have found occasional issues with stability, but those were in general caused either by custom developed code or issues in the implemented architecture.

When the application is installed in servers without the necessary requirements in terms of hardware specs, users may experience slow page loads and perhaps even systems not responding.

Usually, when integrating with other Adobe Marketing Cloud products, we encountered some stability issues, but those are already being worked upon by Adobe.

Yes, we faced issues in one of the projects where we had 50 million users and each user had a lot of personalized pages. (This issue was found when I was working in the CQ Version 5.5, after that, I didn't have any such requirements.)