That video should be available within a few weeks, so stay tuned.
Also, Anthony Molinaro from OpenX will be speaking at RICON, the distributed systems developer conference we're hosting i October. Tickets are still available :)
Also do you have an equivalent page to this (http://www.10gen.com/presentations) . Basically a page that lists every presentation and videos that speak about riak.
Seriously, in my experience Riak is absolutely nothing but AWESOME. If you actually understand CAP and know what you want out of a system, Riak is a great for what it does. Probably best in class.
Yes, they do have some strengths like predictable performance and easy administration but they still have to improve on things like:
- weak data model
- difficult query API
- poor single node performance
- small community/weak adoption
If you want just a single node, use Couch or Mongo - Riak wasn't built to work reliably OR quickly on a single node; Riak gets all of its fault-tolerance, low-latency, and great performance from > 3 node clusters (preferably > 5).
Weak data model is by design. It's a Key/Value store - if you need something more complex then it isn't the right fit for you; Riak is not meant to replace relational databases.
Small community? Certainly not. Weak adoption? Definitely not. Adobe is using Riak, Braintree, and hundreds of other LARGE companies.
The query API is pretty easy to use from the clients in my experience. If you want REAL performance you can write Erlang map/reduce workers - which admittedly gets more complicated but you get far more performance out of that than doing it in JS (which is limited on ANY platform, no just Riak).
Your gripes really aren't legitimate, purely because you're not understanding the use-case for Riak.
We use riak for ONLY TWO pieces of data in our app (out of hundreds of pieces). Everything else is in a relational database. Riak is perfect for FAST GROWING data that maps to the Key/Value model very easily; I can't even begin to describe how perfect Riak is for that. Everything else fits into MySQL/PostgreSQL perfectly and without a hitch. Our fast growing data is handled purely by Riak and Map/Reduce using Erlang workers is FAST.
I am in the process of evaluating riak for an project, and have run across this too. I am not sure if it is specific to the eleveldb backend (I just used the default values so far), or just a bad config on my part. Even when I relaxed consistency down to r=1,w=1 and used the protobuf interface, riak was still performing rather slowly (compared to some other things I am testing) in single node performance.
Because we were a startup using it for about one year and paying the minimum price (I believe around $50/mo) plus another $15 fee/mo, plus they kept 6% of our transactions for 6 months (which we haven't seen any of it yet). Thankfully Stripe came into play (just as easy to implement) with zero monthly fees, and not holding any of our money. At that point we contacted Braintree to cancel our account and just then they offered a lower monthly fee (I believe around $20) and when I said no, they offered to match Stripe at zero cost. Why wouldn't they have offered this from the get go is beyond me and bad practice.
Really loving braintree, haven't checked out stripe, but I think for what we are doing braintree are totally awesome. There has to be a reason why basecamp and others are using them for example. I guess everyone has their reasons to like or dislike something, and valid to have both opinions but we love it.