NIRD TS vs NIRD DL

NIRD consists of two separate storage systems, namely Tiered Storage (NIRD TS) and Data Lake (NIRD DL).

NIRD TS has several tiers spanned by single filesystem and designed for performance and used mainly for active project data.

NIRD DL has a flat structure, designed mainly for less active data, sharing data across multiple projects, and interfacing with external storages.

Both are based on IBM Elastic Storage System.

Architecture comparison

	NIRD TS	NIRD DL
Tiers	Performance and capacity tiers Automatic, transparent tiering Dedicated pools for metadata	Flat architecture (no tiers)
Designed for	- active project data - data processing - AI workloads	- less active data - data libraries - sharing data across multiple projects - interfacing with external storages
Data integrity secured by	- erasure coding - snapshots - backup[1]	- erasure coding - snapshots

	NIRD TS	NIRD DL
Protocols	POSIX, GPFS and NFS	POSIX, GPFS and S3[2]
APIs	GPFS, Discover REST API[3]	GPFS, S3, Discover REST API[3]
Possibilities for	- file access logs -data insight: metadata harvesting[3]	- file access logs - data insight: metadata harvesting[3] - encrypted projects
Access controls	- ACLs - extended attributes	- ACLs - extended attributes - RBAC via S3[2]

–