Choosing the Right Database
Artifactory supports the following pluggable database implementations allowing you to change the default to use other popular databases:
- Derby (the default embedded database, no additional configuration needed)
- PostgreSQL v13.x and below (9.5 and 9.6 are EOL)
- MySQL v5.5 to v5.7 with InnoDB
- Oracle versions v.12.2, v.18, and v.19
- Microsoft SQL Server 2008 (10.5) and above
- MariaDB versions 10.2.9-10.4 and version 10.5.9 (Refrain from using MariaDB 10.5.x versions other than version 10.5.9 due to this known issue).
For each of the supported databases you can find the corresponding example values in the
system.yaml configuration file.
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 a heavy load, you may want to consider using an external database such as PostgreSQL or MySQL, 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.
Artifactory uniquely stores artifacts using checksum-based storage. For details, please refer to Checksum-Based Storage.
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