Apache Sling Content Distribution ships content changes from one repository to another — typically from an authoring instance to one or more publish instances — as versioned, replayable packages instead of ad-hoc JCR writes.

An exporter agent packages changed nodes on the source, an importer agent applies them on the target, and a queue in between makes delivery durable and retryable.

The classic setup is author → publish: editors work on a private author instance, and only reviewed content is distributed out to one or more publish instances that serve traffic.

Distribution also supports reverse flows (publish → author, for user-generated content) and fan-out to many publish farms behind a load balancer.