9 ms·
Riak and the demise of Basho
- EGreg 9y agoI thought Riak was the most impressive and useful open source database until CockroachDB. Would like to see it continue!
- sitepodmatt 9y agoIronic that the posted link returns a 500 "Error establishing a database connection"
- jefozabuss 9y agoThe link points to a news site which probably is not that well provisioned.
- notyourday 9y agoState of the internet in 2017: News sites that does not use caching. In 2017. Let that sink in.
- cies 9y agoSeems to be a little too much traffic for their database. Here's a link to a cached version by Google. http://webcache.googleusercontent.com/search?q=cache:http://www.casinoguardian.co.uk/2017/08/25/bet365-acquires-nosql-database-developer-basho-technologies-remaining-assets/ http://webcache.googleusercontent.com/search?q=cache:http://...
- StavrosK 9y agoThat loaded very slowly for me as well. Here's a prettified IPFS-hosted version: https://www.eternum.io/ipfs/Qmeh3XePHFqRxFiK56Apy3WdVXNw2YVGXWR1Er3t28fTPE/ https://www.eternum.io/ipfs/Qmeh3XePHFqRxFiK56Apy3WdVXNw2YVG...
- arianvanp 9y agoSeems like a good fit. Bet365 is deeply embedded into the Erlang community.
- cies 9y agoHere a link to their Github: https://github.com/bet365 https://github.com/bet365 Not too much Open Source code released by them. Mainly some forks and two RPC libs.
- deleted 9y ago[deleted]
- flurdy 9y agoThat is only one avenue to open source contributions. They may contribute via individual commits directly to other libraries such as https://github.com/basho/riak https://github.com/basho/riak etc
- cies 9y agoI 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.
- _asummers 9y agoRethinkDB 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.
- koolba 9y agoAre those times for real? You could snapshot the underlying disks and copy them byte for byte orders of magnitude faster than that.
- _asummers 9y agoThe problem was replication across the cluster and getting them to coordinate their values. We eventually did what you suggested in our dev environments so that we didn't lose our sanity. .
- cies 9y agoRiak 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".
- _asummers 9y agoSure, but that said, no other DB Jepsen tested til that point necessitated the kind of gymnastics he had to do to get it to fail. It's pretty solid CS, and it's a shame the project had the end of life that it did. [0] https://aphyr.com/posts/330-jepsen-rethinkdb-2-2-3-reconfiguration https://aphyr.com/posts/330-jepsen-rethinkdb-2-2-3-reconfigu...
- deleted 9y ago[deleted]
- simonvc 9y agoMore importantly, they acquired Russel Brown ( http://basho.com/posts/author/russell-brown/ http://basho.com/posts/author/russell-brown/ )
- russelldb74 9y agoAh they didn't. I went to work for them after I was let go by Basho in January, but have since moved on to general contract work on Riak. I am lucky enough to remain in contact with the people at bet365. My take, for what it is worth, is that this is a very generous gesture from bet365 and it helps the whole community. bet365 really hide their light under a bushel in terms of how big a UK technology success story they are. I'm looking forward to working on the newly open sourced replication code.
- porkchopgobbler 9y agolong live riak_repl
- sitkack 9y agoYou could make a killing getting MDC to work between Riak and BigTable [0] [0] https://cloud.google.com/bigtable/ https://cloud.google.com/bigtable/
- deleted 9y ago[deleted]
- i_have_to_speak 9y agoCoverage by TheReg has more details: https://www.theregister.co.uk/2017/08/25/bet365_to_buy_basho_release_code/ https://www.theregister.co.uk/2017/08/25/bet365_to_buy_basho...
- carapace 9y ago"Bankrupt bit bin biz Basho Technologies" and this gem.
- robotmay 9y agoI've always liked Riak, it seems very sensible. Having more open source stuff related to it will be a good thing.
- unkown-unknowns 9y agoOn a side note that has to be the longest e-mail footer I've seen in a good while. Reminded me of a usenet post from years ago but can't find it now, anyone know which one I mean? While looking for said usenet post I found something else though, here: https://www.slashdot.org/story/18304 https://www.slashdot.org/story/18304
- nailer 9y agoIndeed. Martin: just use a link. Law firms do it so you can too.
- andrew_deane_ 9y agoToday 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. One of the initial questions we have for the community is which OSS license would people like applied to the code? Our thought is the most open and permissive.
- romwell 9y agoGreat! There aren't that many persistent (disk-based) KV-stores out there. I planned to, but didn't get to actually use Riak, and was sad when the company seemed to go down. As far as licensing goes, it would be great to have one that would allow me to link the client code libraries and run the servers without having to worry about anything. If I understand correctly, Apache2 goes way beyond that, while GPL is somewhat ambiguous on that. (Yes, one could implement their own client, but that'd be reinventing the wheel). Thank you for keeping this work alive!
- rurban 9y agoRiak and riak core are already Apache 2. Sounds fine. https://github.com/basho/riak/blob/develop/LICENSE https://github.com/basho/riak/blob/develop/LICENSE https://github.com/basho/riak_core/blob/develop/LICENSE https://github.com/basho/riak_core/blob/develop/LICENSE
- zzzcpan 9y agoLike BSD or MIT licenses? That would be great.
- catwell 9y agoApache 2 is probably the best choice here to avoid potential future issues related to patents.
- exbet 9y agoWould make sense to use the same license as Erlang - Apache2
- _Codemonkeyism 9y agoStill amazed that $66m in funding was not enough.
- michaelbuckbee 9y agoI 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 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?
- hanikesn 9y agoThis is not an acquihire. A lot of developers were already let go quite some time ago from Basho.
- fapjacks 9y agoThen what was it? Genuinely curious what happened here...
- icedchai 9y agoFrom that post, it sounds like an asset acquisition. In other words, they bought IP: source code and any related rights.
- tptacek 9y agoThe note mentions a receiver, which means the company is being liquidated by a court, which implies that it's effectively (though not technically) bankrupt.
- wlesieutre 9y agoI didn't specifically ask, but from what I understood they were all gone and this is just assets. Plus a lot of talented people jumped ship before it sank on account of the management team.
- 9y ago
- ulkesh 9y agoThis really doesn't surprise me. My experience with Riak (admittedly in 2012-2014) was that it did not live up to the hype. As strictly a key-value store, it wasn't bad, but toss in 2i, etc, and it quickly became problematic. Open sourcing the software will surely be a good thing, though. I'm eager to see where it leads.
- aetherson 9y agoI worked with riak pretty extensively in that time period. I'm in more or less the same boat. It had cool features, but they didn't make up for the overall kind of slow performance and limited feature-set. (Admittedly, our use of riak was clearly a case of premature optimization: we didn't have anything like the scale to require an available data-store.)
- macintux 9y agoAs a technical evangelist for Basho, I would encourage sales prospects to think carefully about what they really needed. One of the problems trying to sell Riak is that, unless you know you need the availability it can offer at the scale it can support, you're probably better off choosing something with more features and less scale. And, although clearly we're swimming in more data than ever, not all that many people have both massive data sets and a burning need to never lose any of it. A lot of data can be lossy without any real consequence.
- adityapatadia 9y agoI evaluated it in early 2011. At that time all NoSQL dbs were new in market. For me, their restriction on usage in cluster mode, very less support for all languages and lack of file storing abilities like GridFS of Mongo made it unattractive. Eventually Mongo seemed good choice because it was completely free for any kind of use with amazing features and lots of libraries. I am glad I made that decision :)
- joaodlf 9y agoI have no experience with Riak, but I once went to a conference (a very short while ago) and saw a presentation by a higher up of Basho (I won't disrespect the person by naming them), in short: It was a very generic, bland and positively abstract presentation about big data. Other presentations were highly technical, so I was excited to get to know Basho as well - I came out of that thinking "wtf was this guy talking about?". It's obviously not a reflection of what Basho stood for, or even what the individual in question stood for, but that's the only memory Basho has left in me.
- macintux 9y agoA shame you were left with that impression. For quite some time, from top to bottom, Basho had quite a reputation for solid technical talks. The distributed systems conference RICON was quite excellent. (Disclaimer: former Basho technical evangelist & engineer.) Suggestion for something much more meaty: https://youtu.be/3SWSw3mKApM https://youtu.be/3SWSw3mKApM
- nerpderp83 9y agoI suggest going through all the RICON talks, https://www.youtube.com/user/BashoTechnologies/playlists https://www.youtube.com/user/BashoTechnologies/playlists This talk on LVars by Lindsey Kuper blew my mind https://www.youtube.com/watch?v=8dFO5Ir0xqY https://www.youtube.com/watch?v=8dFO5Ir0xqY
- macintux 9y agoLindsey rocks. She had a recent blog post hit HN. There's a fair number of RICON videos on Vimeo too. One of my all-time favorites from Joe Hellerstein: https://vimeo.com/53904989 https://vimeo.com/53904989
- rasjani 9y agoI've no experience w/ Riak what so ever but years ago I was contacted by hh for an open position at Basho. They where looking for field support engineer to a local gaming company. They would hire me and put me directly to client. Maybe i'd have gotten some training on the Riak, but it was never mentioned during the rounds. All interviews where done remotely. Eventually I did say no to the offer. Some time later, even the guy who interviewed me was out from Basho. Idk, whole process just fell very weird.
- wlesieutre 9y agoI knew a couple of folks in Client Services at Basho, one of whom later moved over to the engineering side. From what he told me, the client services group was a great team to work with and had great management.
- wlesieutre 9y agoMissed edit window, but also definitely trained on the job. Neither one had prior experience with Riak.
- deleted 9y ago[deleted]
- cookiecaper 9y agoBasho has silently gone dark since around Easter, with no indication of anything on their site; it still looks like Riak/Basho are an active, living company. Despite being hosted on basho.com, this is just a post to a mailing list, still not an official account/announcement of anything. I have a client with a support contract and while I don't know for certain that they didn't contact someone within the organization, I know that most people, including myself, found out only when someone asked if we could contact Basho support and they were informed that it wasn't there anymore.
- ErlangSolutions 9y agoFYI Erlang Solutions now offers Riak Support
- wjossey 9y agoIn 2012, I worked on a nine month project to migrate a fairly large hot dataset (10s of TBs) off of SimpleDB and onto Riak. At the time, we were experiencing tens of hours of downtime a quarter, much of which could be attributed to SDB. My favorite story about that migration is that four months into the project, we were moving along nicely and ready to start cutting over to Riak after the Christmas holiday. My office had decided to go out to lunch our last work day before everyone headed off for the holidays, and I received a call from a SDB support team member informing me that we either needed to move off their platform by Christmas Day or they'd have to shut us off (we'd start degrading other customers). Fortunately we were nearly ready to pull off the cutover, so we quite literally cut all of our traffic over on Christmas Eve (one of our busiest days of the year). Over the upcoming years, our database continued to grow and grow, and all the while Riak trucked along. It wasn't always a smooth road, and we certainly had our challenges from time to time, but I have yet to hear of anyone who has used a massive 100TB hot database and not had to do work and maintenance. Throughout the years I used Riak, it served me very well. I'm grateful to the innovative work so many at Basho created during their tenure, and I'm glad to see Bet365 attempt to steward the project to a new phase of its life. If I could toast every last basho employee, I would. Thank you all!
- kstrauser 9y ago> I received a call from a SDB support team member informing me that we either needed to move off their platform by Christmas Day or they'd have to shut us off Wat?! That's an excellent reason to burn fields and salt them.
- wjossey 9y agoI was / am pretty sympathetic to their situation. At that point, SDB was already deprecated in favor of dynamo, and they had been asking us to move off of SDB for over a year (before I had joined the company via acquisition). If someone ever does an oral history of AWS, I'm sure that SDB would be the "grand mistake" they made in their first few years. It was never ready for prime time in the way it needed to be.
- 9y ago
- menacingly 9y agoIn my experience with Riak, it absolutely lived up to its promise of scale, even if single-request speed was never quite as zippy as anyone would have liked. However, the Dynamo design is just borderline unpalatable from a developer's perspective. I enjoy being aware of exactly the trade-offs being made, and Basho was always really open about it, but I don't blame anyone for not wanting to dig deep in the weeds to make it work for fairly common use cases.
- zokier 9y agoIf you are going to open source Riak, then maybe consider donating it to Apache Software Foundation? Maybe not immediately, but in the long term it feels like it would make sense.
- ams6110 9y agoWow that one slipped by me totally. I had no idea Basho was in trouble (though I'm not a Riak user, I have used some of their other erlang projects including webmachine and lager). Glad to hear their code will be open-sourced.
- innocentoldguy 9y agoThis is great news! I've spent the last two years working with Riak. I love its admin tools, and Basho engineers were the best to work with. I'm glad to see Riak live on.