Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Artifactory comes with a built-in embedded Derby database that can be reliably used to store data (metadata) for production-level repositories up to hundreds of gigabytes in size.

However, Artifactory supports pluggable database implementations allowing you to change the default to use other popular databases.

Artifactory currently supports the following databases:

For each of the supported databases you can find the corresponding properties file inside $ARTIFACTORY_HOME/misc/db.

Choosing the Right Database

As the default database, Derby provides good performance since it runs in the same process as Artifactory, however, under intensive usage or high load, performance may be degraded since Artifactory and the database compete for shared JVM resources such as caches and memory. Therefore, for Artifactory servers that need to support heavy load, you may consider using an external database such as MySQL or PostgreSQL which are very common choices in many Artifactory installations.

Any of the other supported databases is also a fair choice and may be the practical choice to make if your organization is already using one of them.

titleAccessing a Remote Database

When using an external database, you need a reliable, stable and low-latency network connection to ensure proper functioning of your system.

When using a fullDB configuration, we strongly recommend a high-bandwidth to accommodate the transfer of large BLOBs over the network.

Modes of Operation

Artifactory supports two modes of operation:

  • Metadata in the database and binaries stored on the file system (This is the default and recommended configuration).
  • Metadata and binaries stored as BLOBs in the database

Checksum-Based Storage

Artifactory uniquely stores artifacts using checksum-based storage. For details, please refer to Checksum-Based Storage.


titlePage Contents

Table of Contents

titleRead more

Children Display