Metadata engine
A metadata engine collects, stores, and analyzes information about data and metadata (data about data) in use within a knowledge domain. It virtualizes the view of data for an application by separating the data (physical) path from the metadata (logical) path so that data management can be performed independently of where the data physically resides. This expands the domain beyond a single storage device to span all devices within its namespace. The main use of a metadata engine is to enable flexible IT infrastructure or environments by making applications more storage aware and conversely, a storage device application or data aware.
A metadata engine collects, stores, and analyzes information about data and metadata (data about data) in use within a knowledge domain.[1] It virtualizes the view of data for an application by separating the data (physical) path from the metadata (logical) path so that data management can be performed independently of where the data physically resides. This expands the domain beyond a single storage device to span all devices within its namespace.
The main use of a metadata engine is to enable flexible IT infrastructure or environments by making applications more storage aware and conversely, a storage device application or data aware.
Purpose
[edit]Metadata engines virtualize the view of data. Combined with client access protocols, such as NFS v4.2 and SMB 2.1 or SMB 3.0 (Samba), a metadata engine can create a global namespace to allow applications to see a logical view of their data and can orchestrate data movement between different types or tiers of storage without disrupting the application's access to its data.[2]
References
[edit]- ^ Kendall, Aaron. "Metadata-Driven Design: Designing a Flexible Engine for API Data Retrieval". InfoQ. Retrieved 25 April 2017.
- ^ Flynn, David (16 March 2017). "Supercharge Your Existing Storage with a Metadata Engine". Data Center Knowledge. Retrieved 25 April 2017.
