A common bottleneck in the delivery pipeline for large organizations is the need to distribute, synchronize, and secure software artifacts and release bundles, across:
- Large, geo-distributed, disparate teams and remote sites
- Large-scale, remote, deployment targets – which can span cloud infrastructure, on-prem, air-gapped environments, or embedded/IoT devices.
JFrog Distribution is a centralized solution that enables automated, fast, secure distribution of software releases to any deployment edge. It enables you to distributed applications in a way that is immutable, compliant, scalable, and efficient – where you can even overcome limited bandwidth and network lag.
JFrog Distribution is tightly integrated with your CI/CD pipeline to allow you to deliver releases with confidence. Join this webinar to learn about:
- Key challenges with software distribution at scale
- JFrog Distribution solution architecture: Signed release bundles, smart replication, efficient network utilization, and more.
- Best practices for accelerating releases and ensuring security and compliance across large-scale deployments
- Key use cases and patterns used by some of the largest organizations in the world to improve developer productivity and release fidelity with JFrog Distribution.
- Solution demo: from 0 to Hero with JFrog Distribution
Following the webinar, these great questions were asked by the audience and might be of interest to you.
Bintray is simply the SaaS solution for distribution while Distribution is the OnPrem solution.
There are more pros for the Distribution service as it works flawlessly with all the other JFrog products.
Distribution doesn't require Xray for itself. Xray will be connected only to Artifactory and when using Distribution, it knows to fetch artifacts that were scanned.
Yes, that is correct. Each Artifactory cluster should have it's own Xray instance.
There are few scenarios for using the edge node. One of them is that the edge will be in the customer network yes.
The signature in Distribution is for the release bundle and not for artifact itself on runtime. The signing here is to verify that the release-bundle is being replicated to right location (that has the public key) and it makes the release bundle immutable (cannot be changed at all)
Edge is a lightweight read-only artifactory instance for handling and hosting immutable release bundles. Edges are deployed closer to production sites/DC. It's only possible to transfer software updates (release bundles) to the Edge nodes through JFrog Distribution. No direct upload or replication is allowed. This ensures data integrity and compliance. I hope this answers your question.
You can create a release bundle and add/remove files before signing the release bundles with the GPG Keys. After signing the release bundles are immutable you cannot edit them.
Yes, You can use JFrog Pipelines to automate and build Pipelines.
Yes, you can defines policies in Xray.
JFrog Distribution and Edge nodes are part of our E+ subscription.