Update README.md

This commit is contained in:
Aaron Boodman
2016-06-06 13:39:16 -07:00
parent 28841ee8c9
commit e798b49284

View File

@@ -75,7 +75,7 @@ Noms should work really well as a backing store for ETL pipelines. Noms-backed E
Noms also should be a natural way to collect, integrate, index, and integrate data from disparate sources.
Due to content-addressing, Noms naturally deduplicates all data, so importers can be trivially simple - just dump coarse-grained snapshots periodically and have only the changes re-processed (see [clients/js/fb](clients/js/fb), [client/js/flickr](clients/js/flickr) for some early examples of this).
Due to content-addressing, Noms naturally deduplicates all data, so importers can be trivially simple - just dump coarse-grained snapshots periodically and have only the changes re-processed (see [samples/js/fb](samples/js/fb), [samples/js/flickr](samples/js/flickr) for some early examples of this).
Metadata in such an enviornment can be modeled non-destructively, as assertions from source object to metadata. Such assertions would be naturally versioned and revertable. They would also be owned by the program that made them, meaning they could be manipulated en-masse, leading to easy experimentation.