Riak at Braintree
basho.com
basho.com
Also, Anthony Molinaro from OpenX will be speaking at RICON, the distributed systems developer conference we're hosting i October. Tickets are still available :)
> - poor single node performance
All performed in serial over protobuf (python riak lib).
The minimum recommended number of nodes is 3; the "ideal" minimum number of nodes is 5.
I am going to try bitcask too, to see if eleveldb was the culprit and could be tuned.
It very well could be a configuration issue. I am still trying a few things to see if I can get an improvement.
Thanks.
http://wiki.basho.com/Benchmarking.html https://github.com/basho/basho_bench
First, I want to apologize that we weren't able to reach out about lower fees sooner than we did. High fixed monthly fees have been imposed by the underlying banks that provide merchant accounts for years. Some banks have recently relaxed those and Braintree, Stripe and others in the industry are now able to take advantage of it.
The reason we were able to waive the fixed fee when you contacted us was not because it was in our discretion the entire time, but because we had only recently been able to get some of those fixed fees removed by the underlying banks. Since that time, we have been proactively contacting hundreds of our customers that would benefit from the new bank structure to offer them lower pricing.
The 6% reserve on your transactions wasn't imposed by Braintree but rather the bank that was providing your merchant account (Braintree is not holding back anyone's money). We work extremely hard to prevent reserves being imposed on our merchants and when it does happen, our intent is to get it removed as soon as possible. Please reach out to us so that we can work on getting your funds released asap.
We could have handled your situation better, and we're sorry that we weren't able to get lower fees to you faster. We've been browbeating banks for years on behalf of startups to get simpler, better fee structures. We've made a lot of progress and think we've had an impact on the industry with things like simpler pricing and card data portability. That said, we recognize there is a lot more work to do, and we will continue to work hard to provide an exceptional payments experience for startups.
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.