Stability is not entirely the responsibility of Nexus. The cloud provider needs to provide stability on the backend side as well. We haven't had any problems and the solution is stable. 

The stability is okay. We've had some storage issues just recently, which wasn't anything to do with Sonatype. If the data is moved from one storage array to another storage array, it takes the database offline and, as a consequence, the application goes offline as well. And then it is labor-intensive to bring the service back. 

It all comes down to their database. It's very sensitive — you really have to talk to it nicely and do things in a very controlled way. We have a whole host of applications and databases running across our storage arrays, and this is the only product that really causes any real grief when we move data from one array to another. The real problem is their proprietary database. Once we got off that, the stability, I reckon, will be a whole lot better.

In the last 12 months we've had about four or five major outages. We had some in the evening, which you might think would be okay. Well, that's fine for the UK, but we operate in Manila, we operate in New Jersey, we operate in Las Vegas; we're pretty much all over the world.

We have been very clever in terms of how we take outages and get them communicated. It is one of those heavily used products and when it is down people are quick to shout.

We have about 500 people using it right now.

The stability of Sonatype Nexus Repository is very good.

I am, personally, quite satisfied with the stability and would rate it 8 out of 10. 

The product has been stable since the deployment. I would rate the stability a nine out of ten. 

It's really stable. We have had no stability problems. The main problem we have is more the stability of our infrastructure rather than stability problems with the application.

It's pretty reliable. Again, just the way the organization is set up, we do not have access to the internet. We don't pull the libraries from outside, through the proxies. We are uploading them manually. But it has been pretty reliable. The only issue we had was our infrastructure setup. With the disk allocation, we have run out of space. That's the only problem we had. But as far as the reliability of the product goes, it is fine.

I haven't had any negative impact so far, so I'm very confident using Nexus in terms of its reliability. Everything that has been a system issue has been some misconfiguration on our side. Nexus is a very robust system in my opinion.

Sonatype Nexus Repository is stable. It's solid.

The stability of the Sonatype Nexus Repository is good, we did not have any performance issues.

I rate the product's stability a seven out of ten. Sometimes, there are challenges in mitigating intermittent incidents. There might be factors such as network issues impacting communication.

It's reliable, of course. That's why we have been using this tool for the last eight years.

It is stable, but one thing that's a drawback is that, whenever they release a new major version, like 3.12 or 3.14 or 3.15, what generally happens is that we wait for at least a month or so before upgrading to that version. Recently-released versions are definitely not stable, and they definitely have room for the improvement there.

We are very satisfied with the reliability. 

With Nexus 2 we have been very happy. For Nexus 3, which we deployed on top of OpenShift, we've had some issues with the storage, but I strongly suspect this is not due to Nexus itself. It's mostly due to the infrastructure we used underneath. It could also be that the product is not tested and the quality is not verified on cloud infrastructures like OpenShift. To be honest, I haven't read about it. But for us, I believe the problem is due to the infrastructure, not so much the product.

That being said, I feel that Nexus 3 is generally less stable than Nexus 2. It's more picky with, for instance, authentication. If you're not authenticated anymore, the user interface is not very friendly to you, and it tends to kick you out or lose your data. More could be done in that area. For instance, with Atlassian products, when you get kicked out due to authentication expiry, you still have a chance to recover what you were working on. Maybe the same could be looked into for Nexus 3.

Thus far, the reliability has been good. I haven't seen any problems with the Nexus software breaking down.

So far we haven't had any issues. But when we go into the container world we might, because we haven't gone into the container world yet.