Artifactory supports the following databases that you can use depending on your requirements:
Embedded Derby database
Warning
Due to restricted functionalities, the embedded Derby database can impact the performance and resilience of your Artifactory instance. Hence, JFrog highly recommends avoiding the usage of the Derby database for your Artifactory production environments.
JFrog Recommends Using PostgreSQL
JFrog recommends that you use an external PostgreSQL database in your production instances. JFrog also includes a PostgreSQL build along with the installers.
In addition, since all the other JFrog products support only PostgreSQL, you can use PostgreSQL with Artifactory to simplify your infrastructure.
Starting from Artifactory 7.84.7, new Artifactory installations support only PostgreSQL in the default installation mode. Artifactory will not start unless you configure the system.yaml file to support non-PostgreSQL database.
shared:
database:
allowNonPostgresql: true
type: <database type>Artifactory supports the following modes of operation:
Metadata is stored in the database, and the artifacts are stored on the file system (this is the default and recommended configuration).
Metadata and artifacts are stored as BLOBs in the database.
Artifactory uniquely stores artifacts using checksum-based storage. For more information, see Checksum-Based Storage.
Accessing 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 full-DB configuration, we strongly recommend a high-bandwidth to accommodate the transfer of large BLOBs over the network.