{"id":50928,"date":"2025-07-27T10:27:30","date_gmt":"2025-07-27T10:27:30","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=50928"},"modified":"2026-02-21T07:42:56","modified_gmt":"2026-02-21T07:42:56","slug":"jfrog-artifractory-architecture","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/jfrog-artifractory-architecture\/","title":{"rendered":"Jfrog Artifractory Architecture"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

JFrog Artifactory Architecture: Comprehensive Overview<\/h2>\n\n\n\n

JFrog Artifactory acts as the core of the JFrog Platform, providing robust, universal artifact management across the software supply chain. Its architecture is modular<\/strong>, scalable<\/strong>, and designed to fit both standalone and multi-site enterprise deployments.<\/p>\n\n\n\n

Core Components<\/strong><\/h2>\n\n\n\n
Component<\/th>Description<\/th><\/tr><\/thead>
Artifactory Application<\/strong><\/td>The main server application, handling REST\/API requests, artifact management, replication, and all core functions. Requires a DB and filestore to operate.<\/td><\/tr>
Database<\/strong><\/td>Stores all metadata: user info, permissions, repo configs, artifact paths\/names, and platform configuration. Recommended to use an external SQL DB (PostgreSQL, MySQL, etc.) for production.<\/td><\/tr>
Filestore (Binary Store)<\/strong><\/td>Stores only the actual binaries (artifacts) themselves, organized by checksums (e.g., SHA-1). May use local storage, NFS, or cloud object storage (AWS S3, GCS, Azure Blob).<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Microservices (JFrog Platform, v7+)<\/strong><\/h2>\n\n\n\n
Service<\/th>Functionality<\/th><\/tr><\/thead>
Router<\/strong><\/td>Service discovery and internal API gateway, handling all traffic routing across microservices and products.<\/td><\/tr>
Access<\/strong><\/td>Authentication, access control, group\/user management, and access token issuance for all platform services.<\/td><\/tr>
Frontend<\/strong><\/td>The user interface serving the web UI for all JFrog products in the deployment.<\/td><\/tr>
Topology<\/strong><\/td>Manages platform topology, service registry, and node discovery within clustered deployments (from v7.104).<\/td><\/tr>
One Model<\/strong><\/td>Central API model for all JFrog entities, providing consistency and a unified GraphQL API.<\/td><\/tr>
JFConnect<\/strong><\/td>Manages subscription, licensing entitlements, and cloud checks.<\/td><\/tr>
Event<\/strong><\/td>Handles platform-wide webhook and event distribution for automation and integrations.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

High Availability & Scalability<\/strong><\/h2>\n\n\n\n
    \n
  • HA Cluster:<\/strong> In enterprise mode, Artifactory nodes are grouped behind a load balancer. Nodes share the same external database and filestore, ensuring redundancy, failover, and horizontal scalability. Sessions are stateless, so users or jobs can connect to any node.<\/li>\n\n\n\n
  • Replication:<\/strong> Both unidirectional and bidirectional (federated) repository replication supported for DR, multi-site collaboration, and distributed pipelines.<\/li>\n\n\n\n
  • Edge Nodes:<\/strong> JFrog Edge servers enable caching and distribution closer to remote teams; critical for global or hybrid SaaS setups.<\/li>\n<\/ul>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    \"\"<\/figure>\n\n\n\n

    Deployment Models<\/strong><\/h2>\n\n\n\n
      \n
    • Single Node:<\/strong> All services deployed on one VM\/container, suitable for evaluation, small teams, or edge.<\/li>\n\n\n\n
    • Multi-Node \/ HA:<\/strong> Active-active clusters with externalized DB and filestore for production.<\/li>\n\n\n\n
    • Hybrid\/SaaS:<\/strong> Combines JFrog-managed SaaS core with on-prem or edge nodes for copliance or performance.<\/li>\n\n\n\n
    • Cloud-Native:<\/strong> Supports Kubernetes, scalable object storage, integrations with CSPs.<\/li>\n<\/ul>\n\n\n\n

      Key Platform Workflows<\/strong><\/h2>\n\n\n\n
      \"\"<\/figure>\n\n\n\n
        \n
      • Clients<\/strong> (browser, CI\/CD servers, REST API, CLI, package managers) interact via a load balancer.<\/li>\n\n\n\n
      • Router<\/strong> directs requests to platform microservices or the core Artifactory server.<\/li>\n\n\n\n
      • Authentication & Access<\/strong> is managed by the Access service.<\/li>\n\n\n\n
      • Artifacts<\/strong> are stored in the filestore; all metadata is in the DB. File locations are mapped by checksum.<\/li>\n\n\n\n
      • Replication<\/strong> and event handling<\/strong> allow for automation, integration, and multi-site consistency.<\/li>\n<\/ul>\n\n\n\n

        Architecture Highlights<\/strong><\/h2>\n\n\n\n
          \n
        • Universal Format Support:<\/strong> 40+ package types, broad DevOps ecosystem compatibility.<\/li>\n\n\n\n
        • Stateless Services:<\/strong> Easy to scale both horizontally and vertically.<\/li>\n\n\n\n
        • API-Driven Automation:<\/strong> Extensive REST and GraphQL APIs available for all operations.<\/li>\n\n\n\n
        • Backup\/DR:<\/strong> Backups cover DB + filestore; HA mode is recommended for critical workloads.<\/li>\n\n\n\n
        • Observability:<\/strong> Logging, access auditing, and real-time eventing is integrated.<\/li>\n\n\n\n
        • Governance:<\/strong> Role-based access, compliance, and security scanning (with Xray add-ons).<\/li>\n<\/ul>\n\n\n\n

          Sample High-level Architecture Diagram (Textual)<\/em><\/h2>\n\n\n\n
          text+---------------------+       +-------------------+        +--------------------------+\n|  User\/CI\/CLI\/IDE    +-----> |   Load Balancer   +------> |    Router Service        |\n+---------------------+       +-------------------+        +--------------------------+\n                                                                       |\n         +-------------------------+-----------+----------+---+---+------------------+\n         |   Artifactory App   |   Access   | Frontend | ... | Microservices        |\n         +-------------------------+-----------+----------+---+---+------------------+\n                               |                          |\n                     +-------------------+      +-----------------------+\n                     |    Database       |      |     Binary Filestore   |\n                     +-------------------+      +-----------------------+\n<\/code><\/pre>\n\n\n\n
          Summary Table: Artifactory Architecture Capabilities<\/strong><\/h2>\n\n\n\n
          Capability<\/th>Description<\/th><\/tr><\/thead>
          Artifact Storage<\/td>Highly scalable & pluggable filestore; all binary assets managed via checksum<\/td><\/tr>
          Metadata Management<\/td>Relational DB for all config, repo, and artifact metadata<\/td><\/tr>
          Multi-tenancy & RBAC<\/td>Fine-grained role\/access control throughout<\/td><\/tr>
          API\/Automation<\/td>Full-featured REST API, scripted automation, and webhook\/event platform<\/td><\/tr>
          Scalability & HA<\/td>Active\/active cluster mode with shared DB\/file store; seamless failover, rolling upgrades<\/td><\/tr>
          Multi-site\/Edge<\/td>Support for federated and replicated topologies; edge node distribution for global organizations<\/td><\/tr>
          Security & Compliance<\/td>Encrypted storage, access controls, audit logs, optional integrated scanning and policy engines (via JFrog Xray)<\/td><\/tr>
          Observability<\/td>Unified logs, queryable event streams, and usage dashboards<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
          JFrog Artifactory\u2019s architecture is engineered for performance, robustness, and flexibility, making it suitable for everything from small teams to the largest, most demanding global enterprises.<\/p>\n\n\n\n
          Here\u2019s an overview of the JFrog Artifactory Architecture<\/strong> with its core components and how they interact:<\/p>\n\n\n\n
          \n\n\n\n
          \u2705 Key Components of Artifactory Architecture<\/strong><\/h2>\n\n\n\n
          1\ufe0f\u20e3 User Interfaces<\/strong><\/h3>\n\n\n\n
            \n
          • Web UI:<\/strong> For admin and user interaction.<\/li>\n\n\n\n
          • REST API:<\/strong> For automation and integrations.<\/li>\n\n\n\n
          • JFrog CLI:<\/strong> Command-line interface to manage artifacts.<\/li>\n\n\n\n
          • CI\/CD Tools:<\/strong> Jenkins, GitLab, Azure DevOps, etc.<\/li>\n<\/ul>\n\n\n\n
            \n\n\n\n
            2\ufe0f\u20e3 Access Layer<\/strong><\/h3>\n\n\n\n
              \n
            • Load Balancer \/ Reverse Proxy:<\/strong> Routes traffic to Artifactory nodes (used in HA).<\/li>\n\n\n\n
            • Authentication & RBAC:<\/strong> SAML, LDAP, OAuth, API tokens.<\/li>\n<\/ul>\n\n\n\n
              \n\n\n\n
              3\ufe0f\u20e3 Application Layer<\/strong><\/h3>\n\n\n\n
                \n
              • Artifactory Core Service:<\/strong> Handles repository management, metadata, and artifact lifecycle.<\/li>\n\n\n\n
              • Router Service:<\/strong> Manages API routing and internal service communication.<\/li>\n\n\n\n
              • Metadata Service:<\/strong> Stores artifact properties, build info, checksums.<\/li>\n\n\n\n
              • Replication Service:<\/strong> Manages syncing between instances and federated repositories.<\/li>\n<\/ul>\n\n\n\n
                \n\n\n\n
                4\ufe0f\u20e3 Storage Layer<\/strong><\/h3>\n\n\n\n
                  \n
                • Filestore:<\/strong> Stores actual binaries (local disk, NFS, or cloud object storage like S3, Azure Blob).<\/li>\n\n\n\n
                • Database:<\/strong> Stores metadata, configurations, permissions.\n
                    \n
                  • Recommended:<\/strong> PostgreSQL for production.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                  • Checksum Storage:<\/strong> Deduplicates identical artifacts using SHA1\/MD5.<\/li>\n<\/ul>\n\n\n\n
                    \n\n\n\n
                    5\ufe0f\u20e3 Repository Types<\/strong><\/h3>\n\n\n\n
                      \n
                    • Local:<\/strong> Internal artifacts.<\/li>\n\n\n\n
                    • Remote:<\/strong> Cached external dependencies.<\/li>\n\n\n\n
                    • Virtual:<\/strong> Unified access endpoint.<\/li>\n\n\n\n
                    • Federated:<\/strong> Cross-instance sync.<\/li>\n<\/ul>\n\n\n\n
                      \n\n\n\n
                      6\ufe0f\u20e3 High Availability (HA) Architecture<\/strong><\/h3>\n\n\n\n
                        \n
                      • Multiple Artifactory Nodes:<\/strong> Active-active cluster for redundancy.<\/li>\n\n\n\n
                      • Shared Filestore:<\/strong> NFS or Object Storage accessible by all nodes.<\/li>\n\n\n\n
                      • External Database:<\/strong> Single source of metadata for all nodes.<\/li>\n\n\n\n
                      • Load Balancer:<\/strong> Distributes requests.<\/li>\n<\/ul>\n\n\n\n
                        \n\n\n\n
                        7\ufe0f\u20e3 Integrations<\/strong><\/h3>\n\n\n\n
                          \n
                        • JFrog Xray:<\/strong> Security scanning and license compliance.<\/li>\n\n\n\n
                        • JFrog Pipelines:<\/strong> CI\/CD automation integrated with Artifactory.<\/li>\n\n\n\n
                        • JFrog Distribution:<\/strong> Signed, immutable release distribution.<\/li>\n\n\n\n
                        • Third-Party Tools:<\/strong> Kubernetes, Helm, Terraform, Docker.<\/li>\n<\/ul>\n\n\n\n
                          \n\n\n\n
                          \u2705 Workflow Overview<\/strong><\/h2>\n\n\n\n
                            \n
                          1. Developer\/CI pipeline pushes artifact to Artifactory.<\/li>\n\n\n\n
                          2. Artifactory stores the binary in the Filestore and metadata in the DB.<\/li>\n\n\n\n
                          3. Metadata services manage indexing and checksum validation.<\/li>\n\n\n\n
                          4. Users or pipelines fetch artifacts via the Web UI, API, or CLI.<\/li>\n\n\n\n
                          5. In HA, requests go through Load Balancer \u2192 Artifactory Nodes \u2192 Shared Storage.<\/li>\n<\/ol>\n\n\n\n
                            \n\n\n\n
                            This diagram represents the architecture of JFrog Artifactory<\/strong> and how different components interact. Here\u2019s an explanation of each part:<\/p>\n\n\n\n
                            \n\n\n\n
                            \u2705 Top Layer \u2013 Interfaces<\/strong><\/h2>\n\n\n\n
                              \n
                            1. JavaEE Web Application<\/strong>\n
                                \n
                              • The Artifactory server application built on JavaEE standards.<\/li>\n\n\n\n
                              • Provides the web-based admin and user interface.<\/li>\n\n\n\n
                              • Acts as the core platform to serve all user and API requests.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                              • UI<\/strong>\n
                                  \n
                                • The User Interface<\/strong> (web-based dashboard).<\/li>\n\n\n\n
                                • Allows browsing repositories, uploading\/downloading artifacts, and managing configurations via HTTP.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                                • WebDAV<\/strong>\n
                                    \n
                                  • Web-based Distributed Authoring and Versioning.<\/li>\n\n\n\n
                                  • Enables mounting Artifactory as a network drive for easy drag-and-drop artifact management via HTTP.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                                  • REST API<\/strong>\n
                                      \n
                                    • Provides programmatic access to Artifactory functionality.<\/li>\n\n\n\n
                                    • Used by CI\/CD pipelines, automation scripts, and integrations.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
                                      \n\n\n\n
                                      \u2705 Middle Layer \u2013 Core Services<\/strong><\/h2>\n\n\n\n
                                        \n
                                      1. Caching<\/strong>\n
                                          \n
                                        • Temporarily stores frequently accessed artifacts.<\/li>\n\n\n\n
                                        • Improves performance and reduces repeated requests to remote repositories.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                                        • Virtual Filesystem<\/strong>\n
                                            \n
                                          • Provides a unified, logical file structure to users.<\/li>\n\n\n\n
                                          • Aggregates artifacts from local, remote, and virtual repositories under a single namespace.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                                          • Transactions<\/strong>\n
                                              \n
                                            • Ensures atomic operations (upload\/download) are consistent.<\/li>\n\n\n\n
                                            • Handles concurrent requests without data corruption.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                                            • Security<\/strong>\n
                                                \n
                                              • Manages authentication, authorization, and role-based access control (RBAC).<\/li>\n\n\n\n
                                              • Integrates with LDAP, SAML, OAuth, and API tokens.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                                              • Business Logic<\/strong>\n
                                                  \n
                                                • Implements Artifactory’s core repository management rules.<\/li>\n\n\n\n
                                                • Handles artifact promotion, replication, checksum validation, and metadata processing.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
                                                  \n\n\n\n
                                                  \u2705 Bottom Layer \u2013 Connectors and Storage<\/strong><\/h2>\n\n\n\n
                                                    \n
                                                  1. HTTP Connector<\/strong>\n
                                                      \n
                                                    • Manages communication between Artifactory and external remote repositories via HTTP.<\/li>\n\n\n\n
                                                    • Responsible for downloading external dependencies and caching them.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                                                    • Data Access<\/strong>\n
                                                        \n
                                                      • Handles interaction with the metadata database using JDBC.<\/li>\n\n\n\n
                                                      • Ensures artifact metadata, configuration, and permissions are stored reliably.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                                                      • Remote Repositories<\/strong>\n
                                                          \n
                                                        • External artifact sources (e.g., Maven Central, npm registry, PyPI).<\/li>\n\n\n\n
                                                        • Artifactory proxies and caches these via remote repositories.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                                                        • Databases<\/strong>\n
                                                            \n
                                                          • Stores metadata, configuration, and access control data.<\/li>\n\n\n\n
                                                          • Supported DBs:\n
                                                              \n
                                                            • MySQL<\/strong><\/li>\n\n\n\n
                                                            • Oracle<\/strong><\/li>\n\n\n\n
                                                            • Microsoft SQL Server<\/strong><\/li>\n\n\n\n
                                                            • PostgreSQL<\/strong> (recommended)<\/li>\n\n\n\n
                                                            • Apache Derby<\/strong> (for testing, not production)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
                                                              \n\n\n\n
                                                              \u2705 How It Works Together<\/strong><\/h2>\n\n\n\n
                                                                \n
                                                              • Users or CI\/CD tools<\/strong> interact via UI, WebDAV, or REST API.<\/li>\n\n\n\n
                                                              • Requests go through caching and virtual filesystem layers.<\/li>\n\n\n\n
                                                              • Local artifacts<\/strong> are served from storage; external artifacts<\/strong> are fetched via HTTP connectors from remote repositories.<\/li>\n\n\n\n
                                                              • Metadata is stored in the relational database via the Data Access layer.<\/li>\n\n\n\n
                                                              • Security and business logic ensure access control and artifact lifecycle management.<\/li>\n<\/ul>\n\n\n\n
                                                                \n\n\n\n
                                                                <\/p>\n","protected":false},"excerpt":{"rendered":"
                                                                JFrog Artifactory Architecture: Comprehensive Overview JFrog Artifactory acts as the core of the JFrog Platform, providing robust, universal artifact management across the software supply chain. Its architecture is modular, scalable,… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[4879],"tags":[],"class_list":["post-50928","post","type-post","status-publish","format-standard","hentry","category-artifactory"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/50928","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=50928"}],"version-history":[{"count":2,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/50928\/revisions"}],"predecessor-version":[{"id":59257,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/50928\/revisions\/59257"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=50928"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=50928"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=50928"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}