Sonatype Nexus Repository OSS Requests Per Day: Hard Limit?

Sonatype Nexus Repository
1

Hey,
is the “Requests Per Day” a hard limit or a recommendation in recent Nexus Repository OSS Versions?

grafik
grafik1410×648 34.1 KB

2

You’re at version 3.76.x which is still the “old” OSS edition where these limits are just a recommendation.

However if you’d update to 3.77+, you’d be facing hard limits of 100000 components and 200000 requests per day. See Community Edition Onboarding for more detailed description of how these limits work.

Because you appear to be exceeding some of these limits, be careful about your potential future Nexus updates. Perhaps you can bring the amount of requests down, perhaps not.
We’re staying at 3.76.1 for now, but we won’t be able to do so forever so we’re now considering what to do going forward.

1 Like
3

Thank you very much for the answer!

4

Hi! Like Petr said, on your version, (<3.76), that’s just a recommendation. With your level of usage, you’d be best served on a PostgreSQL database. Community Edition (3.77+) supports Postgres, so we’d recommend that you upgrade, then migrate your database. Check our documentation to learn more about why we recommend the switch.

https://help.sonatype.com/en/understanding-your-usage.html#why-did-sonatype-add-usage-warnings-for-embedded-databases-

But, also like Petr said, Community Edition has hard limits, which are eliminated when you purchase Pro. There’s a grace period and we have promotional pricing in place to try and make that switch as painless as possible. The link Petr shared (Community Edition Onboarding) is the place to start.

5

By the way, I tried just that a while ago and didn’t get much far.
For example, today, I’ve had a call with some account manager and the whole affair was pretty much useless to put it mildly.

Before the call, I’ve already provided a pretty good description of our situation including some recent usage statistics and expectations and needs for the near future, but was still asked the same questions again as if the person didn’t know anything about that. In general, the whole communication was stuck around him continuously wanting to present (promote) the features and capabilities of the Pro edition while I kept repeating that we know about these already and aren’t interested in this topic. He also deliberately avoided providing any price quote and only briefly mentioned the standard price that’s available at your website.

So pretty disappointing exchange so far and if we wouldn’t be using Nexus already, we’d prefer another alternative just based on this experience.

6

Hi, Petr. I’m sorry to hear about that experience. I reached out to our Sales organization and they’ve emailed you with some estimates.

We do our best to make sure that anyone buying a license is completely educated about the features of the product, so that they can maximize their value. I apologize if the experience was frustrating.

If you have more question or need to follow up, feel free to reach out.

7

Hello @jzora, did they use the email address from my profile? I couldn’t find any related message there.

8

Hi @jzora,

I’m confused with the usage limits…

The “Community Edition Onboarding” documentation states hard limits of 200K requests / day and if I go to the “Why did Sonatype add usage warning for embedded databases” documentation there’s a mention to the “Nexus Repository Reference Architectures” which states that Architecture 2 permits 1M requests / day on Community Edition or Pro.

Now, we have exactly the Architecture 2 deployed on premises, using Community Edition v3.81, but I still see the hard limits of 200K requests / day.

Do I need to wait for a new version, or is there inconsistent information across your documentation?

Thanks in advance.

Manuel

9

Hi, Manuel,

The limits you seeing on "Community Edition Onboarding are correct, for all CE users regardless of architecture.

The numbers on the reference architctures page aren’t limits. The table there is to help you pick an architecture that matches your usage. It’s saying, “If you have one million requests, then Architecture 2 is appropriate for you.”

10

If I understood you correctly, there are no software restrictions on the number of requests per day for the oss version? And for the Sonatype Nexus Repository OSS 3.80 version, the number of requests allowed is more than 200,000 per day.

11

What counts towards a “daily request”?

When I use uv (instead of pip), the application makes a lot of requests to look at package metadata (which seems to be coming up as a HEAD request) to compare version data and compatibility with each other. Do those HEAD requests count towards the hard limit?

My CI usage seems to be using a lot more requests than I would expect, even when I’ve cached all the packages I would use locally. I’m trying to figure out where these requests are coming from.

12

Hi Henry,

The detailed explanation of what counts as requests can be found on the Usage Metrics page:
https://help.sonatype.com/en/usage-metrics.html

The HEAD requests you sent out will count towards the hard limit. Essentially, all HTTP requests to /repository/* endpoints would count, including:

  • Any HTTP request (GET, POST, PUT, DELETE, HEAD, etc.)
  • Any response status (200, 404, 500, etc.)
  • Any client type (build tools, browsers, curl, etc.)

Hope this helps.

Best regards,
Grace