Nessie
Nessie is a transactional catalog for data lakes that brings Git-like version control semantics to data.
Our verdict
Who it's for
Transactional catalog for data lakes with Git-like semantics for consistent data views.
Who should look elsewhere
Requires understanding of Git concepts for full utilization
Pros
- +Provides strong data consistency and isolation
- +Simplifies data management in large data lakes
- +Enables safe experimentation and development environments
- +Eliminates manual tracking of data files
- +Efficient as it does not copy actual data
Cons
- −Requires understanding of Git concepts for full utilization
- −Primarily focused on data lake management, not a general-purpose database
Key features
- ✓Git-like semantics for data (commits, branches, tags)
- ✓Always-consistent view of data across all datasets
- ✓Isolated changes for batch jobs and experiments
- ✓Atomic application of data changes
- ✓Automatic garbage collection of unused data files
- ✓Support for multi-table transactions
- ✓References existing immutable data files
- ✓Integration with Apache Hive and Apache Spark
Pricing
| Plan | Price | Billing | Notes |
|---|---|---|---|
| Open Source | — | month | Transactional Catalog for Data Lakes; Git-inspired data version control; Cross-table transactions and visibility |
More in Data & Databases
All →Compare with a peer: Nessie vs Activeloop, Nessie vs Adverity, Nessie vs AfterQuery