lazy-loading

Eclipse Store implements deferred loading using `Lazy<T>` references and lazy collection structures like `LazyArrayList`, `LazyHashMap`, and `LazyHashSet`. These mechanisms wrap large object fields to load data segments on demand rather than all at once.

Eclipse Store lazy collections load collection segments on demand, preventing the entire dataset from consuming memory during application startup. This deferred loading strategy is specifically designed for scenarios involving deep object hierarchies and large datasets.

Yes, Eclipse Store provides mechanisms to clear and manage in-memory data safely after lazy loading. This ensures efficient resource usage by allowing you to control the lifecycle of loaded subgraphs and remove data from memory when it is no longer required.

The best way to handle deferred loading of subgraphs in Eclipse Store is to apply `Lazy<T>` references to large object fields. Wrapping fields with Lazy ensures data is loaded only upon access, reducing startup latency and the overall memory footprint.