Arc Forumnew | comments | leaders | submitlogin
1 point by akkartik 1626 days ago | link | parent

I've thought about this as well for a while. Arc's approach seems to be flat files so far, which means any move to multiple servers is terra incognita on some level[1]. I mean to build a nosql system at some point, but I want to do something besides yet another[2] project. I want to understand[3] why we must couple technology stack choices with where we want to be in CAP space[4]. Why can't we have a single project that lets us tweak one knob for RAM vs persistent store, strong vs eventual consistency, and so on? Laying out the design space in one place may give us some chance at least accumulating lessons as we reinvent the wheel.

[1] https://news.ycombinator.com/item?id=5032739. I was overly harsh, but it's still non-trivial.

[2] http://xkcd.com/927

[3] http://arclanguage.org/item?id=17598

[4] https://en.wikipedia.org/wiki/CAP_theorem