Definition
Shared Data-space Architecture ( Distributed System)
A shared data-space architecture organises communication around a shared, persistent collection of data. Components publish records into this space and obtain data through queries, retrieval or registered interests, rather than addressing the components that produced it.
If a published record
remains in the shared space , so that , another component can access it later even when the producer is no longer active. Persistence decouples production and consumption in time; retention, updates and removal follow the data space’s rules. Selected records and operations are shown. A and B obtain stored record
; B also publishes . The records remain available according to the space’s retention rules, independently of these deliveries.
Data-space Boundaries
The space is a logical service, not necessarily one database or server. Its storage may be partitioned or replicated, with explicit rules for concurrent access and consistency.
Unlike OS shared memory, components need not map the same physical pages. They interact through a shared-data interface, potentially across computers.
Event-based architecture emphasises routing published events to interested components; shared data-space architecture emphasises access to retained data. Event services can also persist events, so persistence alone does not make the styles mutually exclusive.