Publishing architecture

Publishing involves a number of subprocesses, each of which performs a specific task. Publishing is multi-threaded and facilitates distribution to multiple destinations, such as data centers, web servers and so on.

The following diagram shows the various parts of the publishing process:

In the Content Manager environment, publishing comprises the following subprocesses:

Publish Engine
The Publish Engine interacts with Topology Manager to obtain mappings for the Publication, which includes instructions for where and how to send the content.
It then generates Publish Transactions based on the selected Target Type and associated Purpose and puts them in the Publish Queue.
Publisher service
The Publisher Service performs the actual publishing of content in Tridion Sites.
Transport Service
The Transport Service assembles items to be published (and any dependencies) into a Transport Package, which it then transports from Content Manager to the Content Deployer in the Content Delivery environment.
Before sending the package, the Transport Service requests the URL of Content Deployer from the Discovery Service and uses this URL to send Transport Packages to the Content Deployer Queue over an HTTP or HTTPS protocol.
Content Deployer
On the Content Delivery system, a Content Deployer receives and processes the Transport Package and then passes the processed content to the Storage Layer.
Storage Layer
The Storage Layer handles the storing and retrieving of data to and from the Content Data Store (a file system, relational database, or both). The Storage Layer is configurable so that you can store individual types of incoming items to different databases.