Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21b09282f183e6e

Jump to content

Metadata engine

From Wikipedia, the free encyclopedia

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]
  1. Kendall, Aaron. "Metadata-Driven Design: Designing a Flexible Engine for API Data Retrieval". InfoQ. Retrieved 25 April 2017.
  2. Flynn, David (16 March 2017). "Supercharge Your Existing Storage with a Metadata Engine". Data Center Knowledge. Retrieved 25 April 2017.