Why decreasing component and request limits?

[sevensolutions]

I updated to v3.87.0 and noticed, that the maximum component count decreased from 100k to just 40k and requests from 200k to 100k.
In the release notes you're saying "To better align with our goals"...
So this makes me think: Do you further decrease the limits next month? Do you want to stop the OSS version completely? Whats the long-term plan?

[RoBobik]

I'd also like to know the long-term plan. The wording in the release notes feels like you are intentionally hiding that the limits were significantly decreased. IMO release notes should clearly state that you are decreasing the limits, and state the before and after values.

To better align with our goals of supporting individual developers and small teams, Sonatype Nexus Repository Community Edition now supports up to 40,000 total components and 100,000 requests per day. These adjustments ensure consistent, reliable performance for intended use cases and help maintain Community Edition’s long-term sustainability.

[mikekuzak]

Minio started the same way ... and we know how it ended.

[arp-mbender]

Looks like I'm going to have to start a new, downgraded instance and move everything over... 😡

[dides82]

Luckily we read the release notes prior to upgrading 😅
We spent a month optimizing cache in CI/CD and kubernetes to meet quota limits in june, when they were introduced.
And now we are supposed to optimize further ?
This is not viable for us.
We are either stuck at version 3.86.3 or forced to use another solution now....

[thomasmuders-imtf]

I wonder if anyone at Nexus truly believes that this would lead to people looking into buying a commercially licensed version and not rather look at alternative solutions (paid or not). Who would want to trust a company that does such moves. Additionaly, while the source code is here on github, willingfully obfuscating where the limits come from to not allow people to just "fix" it and compile yourself.

[sevensolutions]

I wonder if anyone at Nexus truly believes that this would lead to people looking into buying a commercially licensed version and not rather look at alternative solutions (paid or not). Who would want to trust a company that does such moves. Additionaly, while the source code is here on github, willingfully obfuscating where the limits come from to not allow people to just "fix" it and compile yourself.

I think the thing is: There are no real alternatives. At least i dont know some 🤔

[arp-mbender]

@thomasmuders-imtf IS the full code for this on GitHub? AFAIK the code here is just the base and doesn't have any limits, but the community edition has additional capabilities and, subsequently, does have limits and isn't open sourced. So it's all a bit... weird?

Or am I missing something?

[thomasmuders-imtf]

@thomasmuders-imtf IS the full code for this on GitHub? AFAIK the code here is just the base and doesn't have any limits, but the community edition has additional capabilities and, subsequently, does have limits and isn't open sourced. So it's all a bit... weird?

Or am I missing something?

No, I think you are correct, but I was not aware. If this doesn't have the limits it would actually be good enough as I don't need all of the functionality, maven only is enough for us.

[mikekuzak]

The funny bit is that they allowed postgres with the CE version now, which is more performant, so you can't blame it on the underlying data store, it worked for years fine with OrionDB and does work with h2, but is better with Postgres, so this is ONLY a push to clamp down on the CE Version.

[arp-mbender]

I think the thing is: There are no real alternatives. At least i dont know some 🤔

Well... you can downgrade and not upgrade...? That's what I did, annoying as it were. All I really need is a proxy for Nuget and an internal docker image repo with a nicer GUI, so I'm probably fine with not upgrading.

EDIT: Not that I'm defending this change - I think it's horrible in what it tries to achieve, but I'm just trying to find solutions.

[georgekaz]

The request limit sucks. We've been using Nexus for a long time as a cache for npm and to host a few modules of our own. We only have a couple of devs, we're a small web team. We use Renovate to try and keep things up to date and that along with Github Actions pipelines will consume the whole 100k allowance. So we're sticking to 3.76 which has no limit. To try some things with Rust/Cargo I've installed a second instance at version 3.86 which is the last to have the 200k limit. Probably I'll just replace that with an open source rust package manager such as kellnr. I don't think the limits will make people upgrade to Pro, they will just work around it.

[pietrekzgor]

A terrible change — and the way it was introduced “quietly” makes it even worse. Good thing I noticed that release note in the documentation, because after deployment I would have completely blocked my team’s work ;/ That’s not how this should be handled — it undermines trust. This should be placed in bold red text at the very top of the documentation. With a note saying: “We don’t like CE users, so we’ll make your life harder :D”

I’ve been using Nexus for many years: several projects; Maven, npm, Docker, and yum repositories; ~10k components; ~150k requests (mostly automated version-change verification checks against the repo).

I don’t have the option to move to Nexus Pro, but I can always look for another repository solution. For now, I’m staying on 3.86.

[aminvakil]

Let's keep in mind nexus was always an freeware project and we have not purchased nexus, so we cannot honestly demand anything from sonatype.

This is indeed sad news for me as well, but I respect whatever decision sonatype makes, we (users of open-source nexus) do not have a contract with them stating they should not have limits on open-source version.

That being said I'm moving away from nexus project as it does not fit my needs anymore, but I'm always thankful to them for this brilliant project which I have used for many years.

[sevensolutions]

Of course we cannot demand it and its totally ok to have limits. We all knew it from the beginning. The only thing is that they are reducing it for no reason and that we dont know whats happening tomorrow.

[corporate-gadfly]

Maybe https://github.com/artifact-keeper/artifact-keeper is a good replacement?