Sonatype Nexus Repository Scalability

Joseph_Lim - PeerSpot reviewer
Principal Engineer at Interos Solutions, Inc.

We haven't reached the scalability stage yet but I'm quite sure that it is pretty solid because as long as you're using a backend that supports high availability, it will be fine. We have around 150 users who are mainly engineers.

View full review »
CS
Project Manager at a recreational facilities/services company with 10,001+ employees

In terms of the scalability, we don't see any real impacts on our internal infrastructure or our internal networking. It runs really well. If we were to add another 500 users on there, I wouldn't see any challenges either. In terms of user accounts, from my perspective, you can scale it really well. We started with about 20 users when we were going through initial testing and piloting. Then we went straight from 20 to 500 and we didn't even notice.

View full review »
Yogesh Fulsunge - PeerSpot reviewer
Senior Consultant at Capgemini

I found that Sonatype Nexus Repository is scalable in multiple cases.

View full review »
Buyer's Guide
Sonatype Nexus Repository
March 2024
Learn what your peers think about Sonatype Nexus Repository. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.
CuneytGurses - PeerSpot reviewer
DevOps Engineer at Sonne Technology, Inc.

I would rate the scalability of this solution a four out of ten. The reason being, it's not very scalable, and significant efforts are required to enhance scalability. There are noticeable limitations that need to be addressed for smoother scalability.Currently, there are approximately forty-eight users working with Nexus Repository in our company. As for future plans, I don't foresee a significant increase in the usage of Nexus Repository.

View full review »
Axel Niering - PeerSpot reviewer
Software Architect Sales Systems at SV Informatik GmbH

We are not using any scaling mechanisms which are provided with this product. We would just use more CPU, something like that. But it's okay. There's not much need for scalability here. Not so many people are accessing the repository right now. So it works fine for us.

There are over 130 end users using this solution. 

View full review »
CA
Engineering Manager at a tech vendor with 10,001+ employees

For Nexus Repository Manager, we are currently in a process to scale it to different sites. When we first deployed the application, we only deployed it to one data center. Now we have the need, more and more, to deploy it worldwide in order for the teams to be able to use it locally. For us, deploying it worldwide is really simple because we deploy the different applications on the different sites and then we can proxy the different repositories.

For Nexus IQ, for the time being, we don't have any problems with scalability because we only have one server available for the whole company.

View full review »
RB
Senior Application Architect at a financial services firm with 10,001+ employees

It's scalable. For our organization's needs it's fine. We have not run into any issues where it caused performance degradation.

View full review »
HR
Senior Software Engineer at Systema GmbH

Currently we run with a hot failover system in each location, which is provided by a load balancer. We only have single-node instances running in each location with the one hot failover node, in case of hardware issues. But we haven't had any problems in the last two years we used Nexus Pro. It's just for our peace of mind, to give some robustness to the system, some additional availability.

Initially, we started off with about two gigabytes of RAM. Based on the size of our system we had to increase that to the current configuration of eight. But it's really not a system that consumes high resources. That's one thing I like about the Nexus installation. I used to evaluate Nexus versus Artifactory and, in my opinion, Artifactory consumed much more resources.

View full review »
BA
Cyber Security & Integration Individual Contributor at a aerospace/defense firm with 10,001+ employees

Sonatype Nexus Repository is scalable, we are able to scale both vertically and horizontally. We haven't had any problems either way.

My current program has about 100 users, but they are not users, but rather a pipeline. The primary user is the pipeline. This solution is used hundreds of times throughout the day by the pipeline.

It's a critical piece of our infrastructure.

View full review »
BP
Co-Founder at Arpa

We have 20,000 to 40,000 end users for the product. It is easy to scale. I rate its scalability an eight out of ten. We use it 24/7.

View full review »
KM
DevOps Practitioner at a financial services firm with 5,001-10,000 employees

The scalability is effective, but it's not as effective as other tools available. Currently, they are only supporting a single data center. They should have the ability to support multiple data centers. That is actual scalability and, in effect, high-availability.

For example, if I have three different instances and I want to maintain high-availability and the scalability of my tool, it needs to be scalable across my DCs, rather than on a single DC.  If that single DC goes down for some reason, then my tool goes down.

If I have ten servers being maintained in a DC, I have to maintain ten others in DC2 and ten more in DC3. If DC1 goes down, I have to bring DC2 up with all ten servers. That means I'm managing 30 servers, where I could be managing ten.

And they should have the capability for automation to refresh from one instance to the other.

View full review »
BC
Architect at a consultancy with 1,001-5,000 employees

If you deploy a single instance, it scales very well due to the storage options that it offers. I can't comment so much on the performance because we have never had more than 100 users using it.

But to scale up, to build a federation of Nexus instances, like we do here - we have a big organization - I don't feel that it's very easy for the same reason I mentioned earlier: the lack of configuration through configuration files; that you have to call an API and manipulate the database to configure Nexus instances. I get the feeling from our admins that it's not easy to scale up. They don't feel confident instantiating tens of these or hundreds of these.

View full review »
AE
Chief, Enterprise Automated Deployment (EAD) Branch at a government with 11-50 employees

It's very scalable.

View full review »
YS
Senior Information Technology Specialist at a financial services firm with 5,001-10,000 employees

We've had no issues, as of now, with the scalability. We have been licensed for 250 users for the Repository and we haven't found any issues. The users' roles are DevOps, pure developers, and some of them are testers. As for deployment and maintenance of the solution, that comes under DevOps. Some of the DevOps guys are supporting the platform as well as doing the builds and setting up the pipelines, etc.

View full review »
Buyer's Guide
Sonatype Nexus Repository
March 2024
Learn what your peers think about Sonatype Nexus Repository. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.