An Overview of Nexus Repository Manager and Its Features

In the context of fast iteration and continuous integration, developers need a system that handles code compilation, dependency resolution, build, and version management automatically. The author is working on Nexus, converting its local storage to AWS S3, and first provides a brief introduction to Nexus (OSS version 3.7.0‑04) before later analyzing its source code, compilation, and deployment.

Nexus is a universal software package repository manager. Instead of downloading artifacts directly from Maven Central, teams can host a private Maven repository that proxies remote repositories and caches artifacts locally, saving bandwidth and time. Nexus fulfills this need, and its OSS version is available at https://github.com/sonatype/nexus-public/releases .

Main Features

Supports major package formats such as Java Maven, Node.js npm, Python PyPI, and Ruby Gems.

Can proxy and cache official repositories like Maven Central and PyPI.

Provides private repositories for internal packages.

Manages component versions, metadata, and indexes.

Offers large underlying storage capacity with high data reliability.

A comparison of binary repository solutions shows JFrog Artifactory and Sonatype Nexus as the main players, both offering commercial and open‑source editions. Nexus 3 represents a major redesign with many architectural changes.

Backend Storage

Nexus stores its data as Components and Assets. Components represent resources such as modules, libraries, or frameworks, while Assets contain the binary data for those components. Both are persisted using a blob storage mechanism, as illustrated in the diagram for creating a blob store.

Repository Management

The open‑source version supports many programming language package formats out of the box. Maven can download artifacts directly from a hosted repository or via a proxy repository, which in turn fetches and caches from remote sources. Repository groups allow Maven to resolve artifacts from multiple repositories seamlessly.

API

Nexus provides an interactive Swagger‑UI documentation interface, enabling easy integration with external systems. The API supports artifact search, asset retrieval, and other operations, and can be used by applications to publish packages. Additional capabilities include permission management, log querying, and bundle management.

Conclusion

Nexus is primarily implemented in Java, Groovy, and JavaScript, forming a full‑stack service. On the backend, it uses Jetty as the application server, Karaf as the OSGi container, and OrientDB as the database. The frontend relies on the ExtJS framework. Nexus also features a plugin system that adds support for Maven, PyPI, Docker, and other formats, and can be extended with custom plugins. As a complex yet well‑structured Java open‑source project, it offers valuable learning opportunities for modern Java technologies.