Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Noms – A versioned, forkable, syncable database

github.com

Post reply on HN
Print view View original

21–30 of 107 posts

Re: Noms – A versioned, forkable, syncable database

#23

Post by alsetmusic »

WayneBro wrote: post #19

How is it that you have 2 reference implementations, written in 2 different cross platform environments, yet there is no support for Windows? Why would I use this if I can't use it everywhere?

Not everyone uses Windows. I will use it because it supports macOS and Linux, the two platforms that I use every day. Not everyone has the same needs.

Re: Noms – A versioned, forkable, syncable database

#24

Post by colemickens »

WayneBro wrote: post #19

How is it that you have 2 reference implementations, written in 2 different cross platform environments, yet there is no support for Windows? Why would I use this if I can't use it everywhere?

... well, from the link... "Noms is supported on Mac OS X and Linux. You can compile a Windows build from source, and it usually works, but isn't officially supported."

Also, supporting Windows is often a pain in the ass compared to Linux/Mac. I don't fault them for not supporting it officially, especially in the project's life.

Re: Noms – A versioned, forkable, syncable database

#27

Post by aboodman »

rpedela wrote: post #2

Very interesting, I think we need a git for data. What is the performance of diffs and merges? What data size does it become too slow?

Noms performs diff and merge in time proportional to size of the diff. The size of the source data is not really relevant.

One way to think of Noms is that is an index optimized for computing diffs.

Here's a screencast that shows off Noms diffing things fast: https://www.youtube.com/watch?v=Zeg9CY3BMes

Re: Noms – A versioned, forkable, syncable database

#29

Post by [deleted] »

rspeer wrote: post #14
aeharding wrote: post #4

Earlier quoted context omitted.

If by "Git for data" you mean accumulate-only (or append-only), immutable data stores... There are already many existing solutions. It's always good to see alternatives, though!

Can you point me at some? Because I've tried a few immutable data stores and been disappointed every time. Given about 10 GB of JSON structures, I keep finding things that can't outperform the boring combo of: * Convert the versioned data to tab-separated values * COPY it into Postgres every time * Hope Postgres can act immutable enough even though it wasn't designed to be The closest I've come to improving this situ…

[deleted]
Post reply on HN