Single Pane and Version Set Replication¶

Digital Rebar supports two distinct replication styles: single pane, and version set replication. This page describes these replication styles, their differences, and how to toggle them on manager endpoints.

Overview¶

Replication in Digital Rebar governs how various resources (such as Machines, Clusters, content, etc.) are synchronized between downstream endpoints and their upstream managers. By default, both replication styles are active, but can be separately toggled.

The two styles serve different goals, and replicate in different directions:

• Single Pane replication prioritizes centralized visibility and management, like a single pane of glass into your system.
• Version Set replication prioritizes controlled, explicit distribution of content through shared catalogs across your endpoint hierarchy.

Single Pane Replication¶

Description¶

Single Pane replication is the mode by which database objects replicate upstream.

In this model:

• Downstream endpoints synchronize database changes upstream to their parent (manager) endpoints.
• Changes propagate up the hierarchy, potentially reaching top-level managers, if single pane is enabled fully upstream.
• Upstream managers aggregate replicated objects from all downstream endpoints.

This acts as a single pane of glass, where manager endpoints present a unified view of all replicated objects across the hierarchy. Changes made at the single pane are replicated downstream.

Behavior¶

• If a Machine, Cluster, or other replicated database object changes on a downstream endpoint, that change is reflected on all upstream manager endpoints.
• Manager endpoints do not need to explicitly request objects; they receive them automatically.
• Replication is continuous and state-driven.

Tradeoffs¶

• Managers accumulate all replicated objects, which can increase database size and processing load.
• Less control over which objects are visible upstream.
• Replication is automatic, so synchronization can happen during inconveniently timed load.

Version Set Replication¶

Description¶

Version Set replication is a controlled replication model based on explicit Version Sets, which replicate content bundles (and other resources) downstream, from manager to downstream endpoint.

In this model:

• Content is defined as required by Version Sets.
• Version Sets are explicitly replicated downstream to endpoints.
• Replication is intentional and scoped, rather than automatic and global.
• Downstream endpoints choose when to replicate by "applying" a Version Set.

Behavior¶

• Only content required by a Version Set is replicated.
• Replication flows from manager to downstream endpoints, not upstream.
• Downstream endpoints do not automatically push local object changes back to managers as part of this model.
• Changes to content at the manager do not automaticlly replicate to downstream endpoints. Replicated content is fetched from shared catalog(s).

Use Cases¶

Version Set replication is ideal for:

• Large-scale or multi-tenant deployments
• Environments requiring strict control over content distribution

Summary¶

Single pane replication provides a consistent, constantly replicated view of downstream database objects into their upstream manager endpoints.

Version set replication is the idiomatic way to consistently replicate necessary versioned content from upstream managers to downstream endpoints.

Disabling Replication Styles¶

In some deployments, it may be desirable to explicitly disable one replication style while leaving the other enabled. This can be done using fields set on the Endpoint object.

Disable Version Set Replication¶

To disable Version Set replication on an endpoint, set:

VersionSetsDisabled: true

When set:

• The endpoint will not participate in Version Set-based replication.
• Version Sets will not be applied or synchronized to this endpoint.
• The VersionSets field on the Endpoint object will be ignored.

Disable Single Pane Replication¶

To disable Single Pane replication on an endpoint, set:

SinglePaneDisabled: true

When set:

• The endpoint will no longer push local database changes upstream.
• Upstream managers will not receive objects from this endpoint.
• The endpoint will no longer contribute to the "single pane of glass" view.