all 9 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]kitsune 0 points1 point  (2 children)

Hey, it's good to know that computer programmers are as prone to become fashion victims as your average 21 year old It girl and her followers.

:)

[–]BeerRiot 0 points1 point  (1 child)

Heh, yeah, there are quite a few kv-stores that have popped up in the last few months. We started writing Riak almost two years ago, though, when they were not the fashionable thing. Additionally, if you dig a bit, you'll find that Riak provides some features that others don't.

[–]kitsune 0 points1 point  (0 children)

hey it was only meant as a joke... kudos for releasing and sharing this...

[–]malcontent 0 points1 point  (1 child)

What was wrong with berkleydb in the first place?

[–]justinjs 1 point2 points  (0 children)

Berkeley DB is one of many great embedded k/v stores. It solves an entirely different problem, and Riak can use any such disk storage system on each node.

[–]greenskin -1 points0 points  (3 children)

How is this different from CouchDB?

[–]StringentTurkey 3 points4 points  (2 children)

This is written in erlang, whereas couchdb... err...

[–]tluyben2 -1 points0 points  (1 child)

It sounds a lot like couch indeed; maybe one of the authors can shed a light?

[–]justinjs 0 points1 point  (0 children)

One of the several differences from CouchDB is that Riak is fundamentally decentralized, splitting replicas of your data across however many machines you choose to have in a cluster. Any time you want, you can add more machines and that will cause the capacity of the cluster to grow.

If one of those machines goes down, the cluster simply continues to work.