Skip to main content

The Experience Edge Connector


A conceptual overview of the Experience Edge Connector.

You use the Experience Edge Connector module to publish JSS sites and content from Sitecore CM (content management) to the highly scalable Sitecore Experience Edge delivery platform. Using the Experience Edge Connector module, you can:

  • Create a specific publishing target for Experience Edge publishing, or you can use the default internet target.

  • Use the same publishing user experience in the Content Editor and Horizon.

  • Publish items and sites using smart publish, incremental publish, and republish.

The fundamental concept of the connector module is that it delivers static content in real-time.

The connector module uses the typical Sitecore publishing processes. A critical difference from regular publishing is that the content is published in a static format to the Experience Edge delivery platform. Publishing in a static format flattens all dynamic content structures in Sitecore (standard values, language fall-backs, rendering data source(s), template inheritance, and so on) at publishing time. The following diagram explains the process:

How the connector fits into the publishing process.

Flattening dynamic content structures means that when value-provider items (standard values items and content used as rendering data sources) are published, all content that depends on them is published automatically. Therefore, publishing a single item can lead to publishing hundreds of items. For example, if you publish a template item, all items based on that template directly or indirectly (through template inheritance) are also published. Another example is that when you publish a content item used as a rendering data source by some page, that page is also published.

The connector does not re-implement Sitecore publishing. If Sitecore publishing ignores an item, the connector does not publish it unless it is captured by the connector logic when it identifies the related items to publish.

The connector module uses a custom Solr index to maintain and track the dynamic paths between items.

The following diagram shows a simplified version of the architecture:

The architecture of the Experience Edge Connector.