Riak 1.2 Officially Released
basho.com
basho.com
Have a cluster A/B/C and want to replace A with an upgraded machine Z? Bring up Z and then: cluster join Z; cluster replace A Z; cluster plan/commit.
Have cluster A/B/C and C irreversibly crashes? Bring up node D from backups of C, and then: cluster join D, cluster force-replace C D, cluster plan/commit. Passive read-repair (or the newer repair logic) will resolve replicas missing from the backup.
I generally hate hidden pricing and using products with it because it generally means the company attempts to charge whatever it can get away with and is afraid of having their clients find or what others are paying.
I think Basho has a ops guy that is tasked specifically with going to these Enterprise companies and helping them with the setup - multi-site replication most likely means there are hundreds or thousands of nodes being deployed and that type of thing is really complex and also tricky to do right (even with Riak, which makes it REALLY easy).
My feeling on the price issue is this: Riak is willing to work with their clients - if you need it, you're going to call them and they basically workout what it is you need and what they can provide (maybe it is just the multi-site addon, maybe it's that plus a ops guy that knows Riak in and out and can get you completely set up worry-free with full-time support).
And, I think you'd be surprised. Multi-site replication is a requirement for companies and applications both large and small.
Don't forget though, if you are in a startup, we have Riak for Startups (http://basho.com/products/riak-enterprise-for-startups/) where you pay what you can.
http://wiki.basho.com/Multi-Data-Center-Replication-Concepts...
What I will say, however, is that it has been worth it. Whenever we need Basho's support, they are on the line and ready to help us. Their staff has been excellent to us and I couldn't be happier about our relationship with those folks.
Whether it is sitting down and talking to them about some what-if scenarios, discussing optimizing our usage, or even reviewing configuration files before we spin up a new cluster -- they've been on the ball. We recently renewed our contract for another year and I can't imagine us not doing that as long as we still use Riak.
http://wiki.basho.com/Multi-Data-Center-Replication-Concepts...
What might be the reasons I'd want to use Riak instead of open source alternatives?
Source tarball: http://s3.amazonaws.com/downloads.basho.com/riak/1.2/1.2.0/r...
why does http://downloads.basho.com/ show different results than the above, for the record?
thanks for the nifty db >:3
http://docs.mongodb.org/manual/tutorial/install-mongodb-on-d...
There's nothing on that page except useless talk and a chart. There are hundreds of other NOSQL highly distributed, available, blah blah blah databases. Why should I choose Riak? Why not MongoDB? CouchDB?
And I challenge you to find a link on that page that tells you anything more. All other links are just as bad: http://basho.com/technology/why-use-riak/ and http://basho.com/technology/architecture/ and http://basho.com/technology/technology-stack/ and http://basho.com/technology/technology-stack/ - The wiki is also not good at all: http://wiki.basho.com/Riak.html
They are just spec sheets and vague sentences. For God's sake, show me a sample project. A to-do app so I can get my head around all these new concepts...
It's been 6th or 7th time in the past year that I've stumbled upon your site and was mildly interested to know more about Riak, but the docs are so horrible that I know "nothing" about it.
I gave a (introductory) presentation (to an undergraduate class) about MongoDB after 10 hours of reading their site and "The Little MongoDB Book"[1] and hacking around with it (that's how good and thorough they explained their system). I'm not sure how much it would take for me to understand enough of Riak to explain it to someone.
That guy also wrote a decent "Little Book" on Redis, which I also found extremely compelling. Please, if you like your product and want to see more people use it, write a better documentation. Or hire Karl Seguin to write one for you!
[1]: http://openmymind.net/2011/3/28/The-Little-MongoDB-Book/
http://pragprog.com/book/rwdata/seven-databases-in-seven-wee... ...this has a section on Riak as well.
Moreover, if you just show someone the API for Riak and what it's capable of doing, you're not really giving them an appreciation of what Riak is about. To an application developer, Mongo's interface is probably much more congenial and full-featured.
I think there's a certain extent to which you either have the problem Riak solves and know why you'd want it, or you don't and no tutorial is going to change that. But that might just be an opportunity for a really creative tutorial.
It hasn't been until two years later that I've actually found a need for it - it handles very specific pieces of our data model that grow rapidly and doesn't need to be queried or indexed in any complex manner. We still use a relational database for user records, profile records, transaction records, etc...
Trying to understand Riak by its documentation is like trying to understand Redis by reading up on ziplists.
Edit:
I'm the author of the two Little books mentioned above. I have no doubt that Riak's documentation can be much more approachable. (and I have a love-hate relationship with writing and would never write for money, so you can't hire me, if you were so inclined)
Your "little" series is a boon to humanity man :(
Now that I know Riak is a different NOSQL db, next time I'll spend more time reading the docs.
Thanks.
The navigation could be improved, though. For instance, on the Concepts page I linked to above it isn't obvious that I'm on an overview page and that each link on the left (buckets, clusters, replications, etc.) leads to another more detailed page rather than a section of the current page.
In contrast, Mongos docs are superb IMO.