Riak and the demise of Basho
21–30 of 102 posts
Re: Riak and the demise of Basho
#22- They raised $60mil (the last round being a Series G for $25mil!)
- They're being sold for what I can only this is a pittance / acquihire by Bet365
- Bet365 is buying them because they're heavily invested in Riak internally
- They're open sourcing the code (likely because they need help)
I'm not trying to disparage anyone here, but this makes my blood run cold.
Is Riak so critical to Bet365 that the right move was to _buy the company_ versus switching to a different storage system?
Is there a NoSQL vendor that's doing well out there?
Should we all just be using Postgres anyway?
Re: Riak and the demise of Basho
#23Today bet365 have signed the agreement to purchase all Basho IP. We expect the agreement to be ratified in the US courts next week. Once cleared, our intention is to open source all code, help rebuild the community and collaboratively take the development of RIAK forward. In the coming weeks we will hopefully answer the questions people have and will be calling on the community to help forge the initial RIAK Roadmap.…
Like BSD or MIT licenses? That would be great.
Re: Riak and the demise of Basho
#24I haven't been following this, but from what I can gather: - They raised $60mil (the last round being a Series G for $25mil!) - They're being sold for what I can only this is a pittance / acquihire by Bet365 - Bet365 is buying them because they're heavily invested in Riak internally - They're open sourcing the code (likely because they need help) I'm not trying to disparage anyone here, but this makes my blood run co…
Re: Riak and the demise of Basho
#25I think Riak properly materialized the NoSQL promise of fully scale-out architectures. Have not seen an open source product that delivers on this (no Mongo does not cut it for me). Sad to see they did not manage to make a business out of it... The bet takers may be a good patron to the project, but ideally it is governed by an independent shop that focuses on further development and marketing.
RethinkDB was good from a distributed systems perspective, but a nightmare to maintain in production. Backups and restores would take 12+ hours on ten gigabytes or so and slow queries would grind the whole system to a halt, which isn't possible in Erlang based systems like Riak due to the preemptive scheduling of the BEAM.
Re: Riak and the demise of Basho
#26I think Riak properly materialized the NoSQL promise of fully scale-out architectures. Have not seen an open source product that delivers on this (no Mongo does not cut it for me). Sad to see they did not manage to make a business out of it... The bet takers may be a good patron to the project, but ideally it is governed by an independent shop that focuses on further development and marketing.
RethinkDB was good from a distributed systems perspective, but a nightmare to maintain in production. Backups and restores would take 12+ hours on ten gigabytes or so and slow queries would grind the whole system to a halt, which isn't possible in Erlang based systems like Riak due to the preemptive scheduling of the BEAM.
Re: Riak and the demise of Basho
#27I haven't been following this, but from what I can gather: - They raised $60mil (the last round being a Series G for $25mil!) - They're being sold for what I can only this is a pittance / acquihire by Bet365 - Bet365 is buying them because they're heavily invested in Riak internally - They're open sourcing the code (likely because they need help) I'm not trying to disparage anyone here, but this makes my blood run co…
How much of a halo do you get from writing a nice post about moving to Postgres? How much of a halo do you get from buying and open sourcing something cool?
Re: Riak and the demise of Basho
#28Earlier quoted context omitted.
RethinkDB was good from a distributed systems perspective, but a nightmare to maintain in production. Backups and restores would take 12+ hours on ten gigabytes or so and slow queries would grind the whole system to a halt, which isn't possible in Erlang based systems like Riak due to the preemptive scheduling of the BEAM.
Are those times for real? You could snapshot the underlying disks and copy them byte for byte orders of magnitude faster than that.
Re: Riak and the demise of Basho
#29Earlier quoted context omitted.
RethinkDB was good from a distributed systems perspective, but a nightmare to maintain in production. Backups and restores would take 12+ hours on ten gigabytes or so and slow queries would grind the whole system to a halt, which isn't possible in Erlang based systems like Riak due to the preemptive scheduling of the BEAM.
Riak builds on theoretical foundation, laid out in Amazon's Dynamo paper. The other NoSQLs did not have this theoretical underpinning, and so they just offer a "best effort".
[0] https://aphyr.com/posts/330-jepsen-rethinkdb-2-2-3-reconfigu...
Re: Riak and the demise of Basho
#30I haven't been following this, but from what I can gather: - They raised $60mil (the last round being a Series G for $25mil!) - They're being sold for what I can only this is a pittance / acquihire by Bet365 - Bet365 is buying them because they're heavily invested in Riak internally - They're open sourcing the code (likely because they need help) I'm not trying to disparage anyone here, but this makes my blood run co…
This is not an acquihire. A lot of developers were already let go quite some time ago from Basho.