Full-DB and Full-DB-Direct Binary Providers

These binary providers save all the metadata and binary content as blobs in the database. The Full-DB binary provider has an additional layer of caching on the filesystem while Full-DB Direct does not have a cache and serves artifacts directly from the database.

Full-DB binary provider template configuration

This binary provider saves all the metadata and binary content as blobs in the database with an additional layer of caching on the filesystem. Caching can improve Artifactory performance since frequent requests are served from the cache-fs before reaching out to the database.

The following sample shows the binarystore.xml configuration file for full-db binary provider.

<config version="v1">
    <chain template="full-db"/>
 </config>

What's in the template?

While you don't need to configure anything else in your binarystore.xml, the following sample shows how the full-db template looks like under the hood.

<config version="v1">
    <chain template="full-db"/>
    <provider id="cache-fs" type="cache-fs">
        <provider id="blob" type="blob"/>
    </provider>
 </config>

For details about the cache-fs provider, see Cached Filesystem Binary Provider. The blob provider saves metadata and binary content as blobs in the database.

Full-DB-Direct binary provider template configuration

This binary provider saves all the metadata and binary content as blobs in the database without a caching layer.

The following sample shows the binarystore.xml configuration file for full-db-direct binary provider.

<config version="v1">
    <chain template="full-db-direct"/>
 </config>

What's in the template?

While you don't need to configure anything else in your binarystore.xml, the following sample shows how the full-db-direct template looks like under the hood.

<config version="v1">
    <chain template="full-db-direct"/>
    <provider id="blob" type="blob"/>
</config>

The blob provider saves metadata and binary content as blobs in the database.