README
¶
[Command-Line Tour](doc/cli-tour.md) | [Go SDK Tour](doc/go-tour.md) | [JavaScript SDK Tour](doc/js-tour.md) | [Intro to Noms](doc/intro.md) | [FAQ](doc/faq.md) | [Project Status](#status)
[](http://jenkins.noms.io/job/NomsServer) [](https://godoc.org/github.com/attic-labs/noms) [](http://slack.noms.io)
Noms is a decentralized database based on ideas from Git.
This repository contains two reference implementations of the database—one in Go, and one in JavaScript. It also includes a number of tools and sample applications.
About Noms
Noms is different from other databases. It is:
-
Content-addressed. If you have some data you want to put into Noms, you don't have to worry about whether it already exists. Duplicate data is automatically ignored. There is no update, only insert.
-
Append-only. When you commit data to Noms, you aren't overwriting anything. Instead you're adding to a historical record. By default, data is never removed from Noms. You can see the entire history of the database, diff any two commits, or rewind to any previous point in time.
-
Strongly-typed. Noms doesn't have schemas that you design up front. Instead, each version of a Noms database has a type, which is generated automatically as you add data. You can write code against the type of a Noms database, confident that you've handled all the cases you need to.
-
Decentralized. If I give you a copy of my database, you and I can modify our copies disconnected from each other, and come back together and merge our changes efficiently and correctly days, weeks, or years later.
## Setup
Noms is supported on Mac OS X and Linux. Windows usually works, but isn't officially supported.
git clone https://github.com/attic-labs/noms $GOPATH/src/github.com/attic-labs/noms
go install github.com/attic-labs/noms/cmd/noms
noms log http://demo.noms.io/cli-tour::sf-film-locations
## Explore
Visually explore a demo instance of Noms
## What Noms is Good For
Data Version Control
Noms gives you the entire Git workflow, but for large-scale structured (or unstructured) data. Fork, merge, track history, efficiently synchronize changes, etc.
noms diff and noms log on large datasets
An Application Database with History
A database where every change is automatically and efficiently preserved. Instantly revert to, fork, or work from any historical commit.
Versioning, Diffing, and Syncing with Noms
An Archival Database
Trivially import snapshots from any format or API. Data is automatically versioned and deduplicated. Track the history of each datasource. Search across data sources.
TODO: Sample and video
## Status
Data Format
We are fairly confident in the core data format, and plan to support Noms database version 7 and forward. If you create a database with Noms today, future versions will have migration tools to pull your databases forward.
Completeness
We're just getting started. Some important features are not yet implemented including a query system, concurrency, auto-merging, and GC.
API
The Public API will continue to evolve. Pull requests which represent breaking API changes should be marked with APIChange and sent to the slack channel and mailing list below for advance warning and feedback.
## Talk
Directories
¶
| Path | Synopsis |
|---|---|
|
cmd
|
|
|
util
This is the Command struct used by the noms utility.
|
This is the Command struct used by the noms utility. |
|
go
|
|
|
hash
Package hash implements the hash function used throughout Noms.
|
Package hash implements the hash function used throughout Noms. |
|
util/progressreader
Package progressreader provides an io.Reader that reports progress to a callback
|
Package progressreader provides an io.Reader that reports progress to a callback |
|
util/status
Package status prints status messages to a console, overwriting previous values.
|
Package status prints status messages to a console, overwriting previous values. |
|
samples
|
|