Architecture Interceptors

Any combination of interceptors can be used to compose the storage driver for a hiperspace, also including domain SubSpace

GenerationSpace

GenerationSpace can be used to partition the current working set from historical versions transparently. Scenarios where you’d choose to do this include:

• Partitioning of daily data form sealed historic versions that do not change after close of day. Historical Spaces can be opened read-only with direct file access without the need for Rockshare
• Distributed history, where read-only data is duplicated on each server for performance.
• Batch processing where an entire day’s data may be reviewed as a whole and merged once approved.

FailoverSpace

A FailoverSpace provides transparent failover to synchronized remote servers

PartitionSpace

PartitionSpace provides hash partitioning of a Hiperspace

SessionSpace

SessionSpace uses two underlying Hiperspace drivers for the session and durable store. When the SessionSpace is closed, the Elements in the Session Space are bulk transferred to the durable store. There are two scenarios where this is useful:

• Transactional session, where objects are added to the session store (typically using the Heap driver) and written to the durable store (provided Abort() hasn't been called)
• Bulk Load session, where a large number of updates are accumulated and transferred as a compressed stream