TECHNOLOGY PROFILE · TECH-0133

lakeFS

Version-control-like operations for object storage.

Reference link only — not reviewed this edition. This profile preserves the prepared catalog’s original descriptions. Advantages depend on the workload; comparisons are editorial, not benchmark results.

Where it has an edge

Branching and commits enable isolated dataset changes without copying entire data lakes manually.

Best-fit problems

Reproducible large dataset versions and safe data-pipeline experiments.

Tradeoffs & cautions

Object-store/catalog integration and operational setup matter.

What to test before choosing

Reproduce a run from its recorded code/data/config; test artifact access, search budget and validation leakage.

Runtime & hardware

Local, server or managed

Access & licensing

Open-source cores; hosted/commercial features vary

Execution

Local / self-hosted

Lifecycle

Not independently audited

Comparison basis

Editorial problem-fit judgement; no head-to-head benchmark performed

Connected concepts

Alternatives to investigate

DVC · Apache Iceberg

Original source

lakeFS — original reference ↗

Compare, save or annotate this profile in the workspace →