Artifactory Product

Artifactory microservices overview: 15+ services including Artifactory Service, Router, Access, Metadata, Topology, and Event.

The Artifactory product includes the following microservices:

MicroserviceRoleAvailability and notes
Artifactory ServiceMain application service.-
RouterCentral communication hub for microservices and products in the JPD.-
AccessAuthentication service and registry for users, groups, permissions, and access tokens across the JPD.-
TopologyService registry for platform topology management (extracted from Access).Available from Artifactory version 7.104.
One ModelCentralized hub for GraphQL APIs that maintains a unified platform entity model and common language across services.Available from Artifactory version 7.104.
EventEvent distribution mechanism for JFrog products. Distributes webhook events to external systems.-
FrontendApplication UI for the entire JPD.Runs as a standalone Kubernetes Deployment by default. See Service Pod Architecture Changes.
JFConnectFetches subscription entitlements into a JPD.See JFConnect Microservice.
MetadataMetadata server for components. Serves the Packages screen in the JPD UI.-
ObservabilityConsolidates logs and metrics in the service.-
JFConfigCentralized key-value configuration storage in the database for JFrog services.Available from Artifactory version 7.111.
EvidenceEnables signing of CRD evidences for artifacts, builds, packages, and release bundles.See Evidence service.
Artifactory Federation Service (RTFS)Synchronizes large volumes of artifact metadata between customer sites.See Artifactory Federation Service.
Mission ControlSingle access point for managing multiple JPDs.Available with an Enterprise+ license. See Installing Mission Control.
JFBusEvent-streaming service for platform-wide event processing and communication.From Artifactory 7.161, enabled by default. Runs as a standalone Kubernetes Deployment on Helm/Kubernetes installations.
JFmeltEvent collection and dispatch pipeline for the JFrog Platform.From Artifactory 7.161, enabled by default (Pro only; requires JFBus and JFConnect); runs as a standalone Kubernetes Deployment on Helm/Kubernetes installations.

Related Services And Configuration

Related Topics



Did this page help you?