The JFrog Platform is a mission-critical tool for building and delivering software. Organizations rely on this enterprise-grade solution to achieve a seamless DevOps experience at scale.
To best meet the needs of customers, JFrog engaged in a thorough evaluation of top database providers’ capabilities and scaling support. Ultimately, PostgreSQL was chosen as the preferred database for all JFrog products.
Key benefits of choosing PostgreSQL for your JFrog deployment include:
A single database engine simplifies the tech stack required to operate the JFrog Platform.
Support for unique PostgreSQL features to improve performance and functionality.
Leverage the experience and massive scale of JFrog Cloud where PostgreSQL is the database used.
JFrog highly recommends using PostgreSQL for all products in the JFrog Platform.
For Existing Installations Using a Non-PostgreSQL Database
There is no impact on existing Artifactory instances using one of the Artifactory supported databases. Artifactory will continue to support Oracle, MySql, Microsoft SQL Server, MariaDB, and Derby.
Migrating to the PostgreSQL database can be done by using various methods. Using our System Import and Export is the most popular one. To ensure a successful and smooth migration to PostgreSQL in large environments, you can reach JFrog experts to plan a migration strategy that is tailored to your use case and ecosystem.
For New Installations Using a Non-PostgreSQL Database
Organizations can still choose to use any database in the list of Artifactory supported databases. However, there is a minor new configuration step that will need to be performed for new installations.
Starting with the Artifactory 7.84 release, when installing a new Artifactory instance with any database other than PostgreSQL, before running Artifactory, you are required to add the following configuration settings to the file $JFrog_HOME/var/etc/system.yaml:
shared:
database:
allowNonPostgresql: true