If you’re running Sonatype Nexus Repository or Sonatype Nexus Repository Community Edition (formerly known as Nexus Repository OSS) on OrientDB, you’re operating on a legacy database architecture that is no longer aligned with current security and platform requirements.
Support for OrientDB in Nexus Repository is now fully sunset. Deployments using OrientDB will no longer be supported.
While issues in newer architectures have been addressed, they cannot be fully remediated within the legacy OrientDB-based stack. The result is a growing gap between what can be secured and what can no longer be maintained.
In this post, we explain:
The Problem: OrientDB Is No Longer Defensible
Older Nexus Repository versions (below 3.70.5) rely on an architecture built around OrientDB and outdated software dependencies.
That stack now carries:
Remaining on OrientDB introduces increasing operational constraints. Security fixes cannot always be backported. Platform innovation is moving elsewhere.
PostgreSQL is now the recommended and actively supported database for Nexus Repository. It offers measurable improvements in performance, better support for high availability and cloud-native architectures, and access to new and future product capabilities not being built for OrientDB.
The Decision: Two Supported Paths Forward
Once you decide to move off OrientDB, there are two supported migration paths forward.
Both approaches eliminate dependence on OrientDB. The difference is how much infrastructure responsibility your team wants to retain.
Option A: Move to Sonatype Nexus Repository Cloud (Recommended)
The fastest and most secure path forward is to move to Nexus Repository Cloud.
Benefits of this move include:
-
Fully managed infrastructure.
-
Automatic updates and patching.
-
Reduced operational overhead.
-
Built-in scalability and resilience.
-
Eliminates database management (Read more...)
