Hey,
is the “Requests Per Day” a hard limit or a recommendation in recent Nexus Repository OSS Versions?
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
Thank you very much for the answer!
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.
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.
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.
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.
Hello @jzora, did they use the email address from my profile? I couldn’t find any related message there.