svn commit: r1731067 - /sling/site/trunk/content/documentation/bundles/content-distribution.mdtext

[mp...@apache.org]

Author: mpetria
Date: Thu Feb 18 13:15:46 2016
New Revision: 1731067

URL: http://svn.apache.org/viewvc?rev=1731067&view=rev
Log:
SLING-4540: content distribution documentation page

Modified:
    sling/site/trunk/content/documentation/bundles/content-distribution.mdtext

Modified: sling/site/trunk/content/documentation/bundles/content-distribution.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/content-distribution.mdtext?rev=1731067&r1=1731066&r2=1731067&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/content-distribution.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/content-distribution.mdtext Thu Feb 18 13:15:46 2016
@@ -4,25 +4,70 @@ Title: Content Distribution (org.apache.
 
 ## Introduction
 
-The Sling Content Distribution (SCD) module allows one to distributw Sling resources between different Sling instances. The API works at path level and the distribution agents basically enable distribution of specific paths between instances. There are several main usecases in which SCD can help.
+The Sling Content Distribution (SCD) module allows one to distribute Sling resources between different Sling instances. The API works at path level and the distribution agents basically enable distribution of specific paths between instances. There are several main usecases in which SCD can help. Typically the distribution is done from one or more source instances to one or more target instances.
 
 ## Distribution usecases
 
 ### Forward distribution
-A "forward" distribution setup allows one to transfer content from an author instance to a farm of publish instances.
+A forward distribution setup allows one to transfer content from a source instance to a farm of target instances. That is done by pushing the content from source to target.
+
+#### Setup overview:
+* one source instance
+** one distribution agent connected to importer endpoints for all target instances.   
+* N target instances
+** one distribution importer on each target instance used to import packages into the local instance.
+
+#### Sample configuration:
+
 
 ### Reverse distribution
 
-A "reverse" distribution setup allows one to transfer content from a farm of publish instances to an author instance.
+A reverse distribution setup allows one to transfer content from a farm of source instances to a target instance. That is done by pulling the content from source instances into the target instance.
+
+#### Setup overview:
+* one target instance
+** one distribution agent connected to exporter endpoints for all target instances.   
+* N source instances
+** one distribution (queue) agent on each source instance; changes from the source instances are placed in the queues of these agents.
+** one distribution exporter on each source instance that exports packages from the queue agent.
+
+#### Sample configuration:
+
+
 
 ### Sync distribution
 
-A "sync" distribution setup allows one to synchornize content in a farm of publish instances.
+A sync distribution setup allows one to synchronize content in a farm of instances. That is done by using a coordinator instance (typically an author instance) that pulls content from all instances in a farm and pushes it back to all.
+
+#### Setup overview:
+* one coordinator instance
+** one distribution agent connected to exporter/importer endpoints for all farm instances.   
+* N farm instances
+** one distribution (queue) agent on each farm instance; changes from these instances are placed in the queues of the queue agents.
+** one distribution exporter on each farm instance that exports packages from the queue agent.
+** one distribution importer on each farm instance used to import packages into the local instance.
+
+#### Sample configuration:
 
 
 ### Multidatacenter sync distribution
 
-A "multidatacenter sync" distribution setup allows one to synchornize content in a farm of publish instances across datacenters.
+A multidatacenter sync distribution setup allows one to synchronize content in a farm of publish instances across datacenters. This a variation of sync distribution but using a coordinator in each datacenter.
+
+#### Setup overview:
+
+* one coordinator instance in each datacenter
+** one distribution agent for intra-datacenter synchronization. Like a regular sync agent it connects to all farm instances in its datacenter and syncronizes them. In addition to a regular sync agent it keeps the packages also in dedicated queues for the other DCs, so that the coordinators from the other DCs can pull the updates.
+** one distribution exporter for each queue dedicated for the remote DCs. The inter-dc coordinators from the other DCs will connect to these exporter endpoints.
+** one distribution agent for inter-datacenter synchronization; it conntects to the dedicated queues exposed by intra-dc coordinators from the other datacenters.
+* N farm instances in each datacenter
+** one distribution (queue) agent on each farm instance; changes from these instances are placed in the queues of the queue agents.
+** one distribution exporter on each farm instance that exports packages from the queue agent.
+** one distribution importer on each farm instance used to import packages into the local instance.
+
+#### Sample configuration:
+
+
 
 
 ## Additional options