Boundbound

Boundbound is a term used in software architecture to describe a data-binding pattern in which a single data source is bound to two or more independent consumer contexts. The pattern is designed to maintain consistency across contexts by propagating updates bidirectionally between the source and each bound context, while preventing circular updates.

Conceptually, boundbound combines elements of two-way binding with multi-context synchronization. A mediator—such as an event bus, a central store, or a reactive stream—coordinates changes. Each bound context subscribes to the mediator and writes back through it, after which normalization prevents feedback loops.

Compared with standard two-way binding to a single consumer, boundbound explicitly supports synchronization across multiple contexts. This can improve user experience in dashboards, collaborative interfaces, and complex UIs where several components must reflect the same state.

Examples include a data model bound to both a chart and a summary panel; updates in either component propagate to the other components consistently. Potential drawbacks include increased architectural complexity, latency concerns, and the risk of subtle synchronization bugs that require careful testing.

See also: data binding, multi-context binding, mediator pattern, reactive programming.