Documentation Center

Decoupling Content Manager and Content Delivery

The decoupling that Topology Manager provides allows you to replace your Content Delivery stack very easily. This is especially useful if you want to replace your on-premise Content Delivery environment with a Cloud-based Content Delivery environment.

In order for users of your Content Manager environment to publish to a new Content Delivery environment, no change to your Content Manager setup is necessary. In fact, so long as the new Content Delivery environment is set up in the same way as the old one (for example, it has a staging and live server just like before), even Topology Manager hardly needs to change. Only one thing needs to be configured: the location of the new Content Delivery environment's Discovery Service, which exposes the Discovery Endpoint, the single entry point to all Capabilities available from that Content Delivery environment.

The result of this is that migrating to a new environment, whether it's a faster cluster of servers, an environment provided by a new hosting provider, or a Cloud-based setup, consists mainly of rigging up the new delivery environment itself. Once it is in place and the Discovery Service URL is known, migration consists of swapping out the reference to the old Content Delivery environment for a reference to the new one in Topology Manager.