1.1: When to Route vs. When to Replicate/Sync External Content

By Optimizely Education
Published: Mar 16, 2026
Rating 1 star 2 stars 3 stars 4 stars 5 stars

Average rating: 0 No reviews

Outline

At a glance

Architectural Decision: Choosing between real-time data access (Partial Routing) and managed data propagation (Synchronization).
Partial Routing: Utilizing IPartialRouter to handle virtual URL segments without duplicating database rows.
Synchronization: Mapping external entities to native PageData/BlockData for maximum editorial augmentation.
Decision Logic: Balancing data volatility, volume, and the need for CMS-side property management.

In the landscape of modern enterprise architecture, Optimizely CMS 13 (PaaS) rarely exists in isolation. It is frequently the centerpiece of a composable ecosystem, surrounded by Digital Asset Management (DAM) systems, Product Information Management (PIM) platforms, Customer Relationship Management (CRM) tools, and external transactional databases. The architectural challenge for a developer is not just how to connect these systems, but how the data should live within the CMS.

We refer to this as Content Federation. There are two primary schools of thought: Partial Routing (where content stays in the source system and is accessed via virtual URLs at runtime) and Replication/Synchronization (where data is copied into the CMS database). Choosing the wrong path can lead to downstream failure modes, such as crippling performance bottlenecks, "stale" content, or a degraded editorial experience. As you prepare for the PaaS CMS 13 Developer Certification, mastering this decision matrix is critical for designing scalable, reliable, and governed integrations.

1. Partial Routing: The Virtual Path

Partial routing is a mechanism in Optimizely CMS that allows you to extend the standard URL routing pipeline. While standard routing maps a URL segment to a PageData object in the database, partial routing allows you to "take over" the remaining part of a URL and map it to a non-CMS entity at runtime.

How it Works: The IPartialRouter Interface

Technical implementation involves the IPartialRouter<TContent, TRoutedData> interface. This interface is generic, allowing you to specify the starting point (entry page) and the resulting model. When the routing engine matches a portion of the URL to a CMS page, it invokes the custom router to handle the "residual" segments by querying an external service.

public class ProductPartialRouter : IPartialRouter<CatalogPage, ExternalProduct>
{
    private readonly IExternalProductService _productService;

    public ProductPartialRouter(IExternalProductService productService)
    {
        _productService = productService;
    }

    public object RoutePartial(CatalogPage entryPoint, SegmentContext segmentContext)
    {
        // Consume segments from the remaining path
        var productSlug = segmentContext.GetNextValue(segmentContext.RemainingPath);
        var product = _productService.GetProductBySlug(productSlug.Next);

        if (product != null)
        {
            segmentContext.RemainingPath = productSlug.Remaining; // Mark segments as consumed
            return product; // This object will now be available in the current context
        }
        return null;
    }
}

Strategic Advantage: The Source of Truth

Partial routing ensures that the external system remains the absolute source of truth. This is ideal for data that is highly volatile, such as inventory counts or live pricing. You avoid the "Dual-Source" problem where the CMS database and the PIM disagree on a price because a synchronization job hasn't run yet. Furthermore, it prevents database bloat by not duplicating large-scale catalogs (e.g., millions of SKUs) into the CMS SQL instances.

2. Replication and Synchronization: The Managed Approach

Replication (or Synchronization) is the process of mapping external data into native Optimizely Content Types (PageData or BlockData). This effectively makes the external content "native" to the CMS ecosystem.

Core Mechanisms in CMS 13 (DXP):

Service-to-Service Integration: Periodic C# jobs or AWS/Azure functions that fetch data and use the IContentRepository to save items.
Event-Driven Sync: Real-time reaction to external webhooks, using the Optimizely Service APIs to upsert content.
Content Graph Integration: Content synced into the database is automatically indexed by Optimizely Graph for headless multi-channel delivery.

Strategic Advantage: Editorial Augmentation

The primary reason to replicate content is to empower marketers. When content exists as a PageData object, editors can add "CMS-only" properties—such as SEO meta-tags, promotional banners, or design layouts—that do not exist in the source system (e.g., a technical ERP database). Since the data is stored locally, page performance is optimized through the CMS caching layer, eliminating runtime API dependencies.

3. The Architectural Decision Matrix

Use the following matrix to guide your recommendation for integration projects in a PaaS environment:

Criteria	Favor Partial Routing	Favor Replication (Sync)
Volatility	High (Prices, Odds, Stock)	Low (Article text, Descriptions)
Volume	Extremely High (1M+ items)	Low to Medium (Under 100k)
Editing	Read-Only / Source Controlled	Needs CMS Property Augmentation
Preview	Difficult (Requires custom rendering)	Native (Works with On-Page Editing)
Search	External Search Needed	Integrated Site Search (Graph)

4. Performance and Graceful Degradation

In a PaaS environment like Optimizely DXP, regional latency can impact partial routers. If your CMS is in Europe and your API is in the US, every page load for a virtual item will suffer a 200ms+ round-trip penalty. To mitigate this risk, developers should implement aggressive caching using the IObjectInstanceCache and provide robust error handling (e.g., custom 404 views or stale-data fallback) if the external API becomes unavailable.

Conclusion

The architectural choice between partial routing and content replication in Optimizely CMS 13 is fundamentally a trade-off between the freshness of data and the reliability of the authoring experience. Partial routing offers a lightweight, runtime-centric window into highly volatile external systems, while replication provides a stable, "native" environment that empowers marketers with full design system capabilities and integrated search functionality. Mastering the decision matrix—evaluating volume, volatility, and editorial intent—is essential for any developer aiming to build resilient content federation strategies that maintain the high performance and governance standards required for an enterprise PaaS implementation.