We’ve been expanding at an impressive rate as of late (we’re trying to keep up with GitHub), and today we’re thrilled to announce that another amazing developer has joined the Basho Team. Join us in welcoming Jared Morrow!
We are pleased to announce that Ryan Zezeski has joined the Basho Team! Ryan has been coding since 14 and was hooked after writing his first program in Visual Basic 3.0 …
March 24, 2011 Adam Hunter is the newest Basho Developer Advocate! Adam first got involved with Riak when he used…
In February we kicked off the KillDashNine drinkup. It was a huge success (turns out we aren’t the only ones who care about durability) and, as promised, we’ll be having another drinkup this month.
There is a group of community members who are given commit access the Riak Wiki repository on GitHub, and I’m pleased to announce that Ryan Zezeski is now part of this group.
We are absolutely thrilled to announce that Mathias Meyer has joined the team here at Basho as a Developer Advocate.
We just added Kevin Burns as a committer to the Basho-supported Riak PHP Client. Kevin has been hard at work over the past few weeks adding some great functionality to the PHP client…
We started Basho Technologies with an idea as simple and timeless as an honest day’s work. Databases shouldn’t lose data. Sounds radical, we know, but some people think losing data is fine as long as they have cool coffee mugs. (By their own admission, these folks have built “databases” that run the risk of losing data if users issue a simple “kill -9” command.)
The Riak Fast Track has been around for at least nine months now, and lots of developers have gotten to know Riak that way, building their own local clusters from the Riak source. But there’s always been something that has bothered me about that process, namely, that the developer has to build Riak herself. Basho provides pre-built packages on downloads.basho.com for several Linux distributions, Solaris, and Mac OS/X, but these have the limitation of only letting you run one node on a machine.
Many thanks to commenter Mike for taking up the challenge I offered in my last post. The flaw I was referring to was, indeed, the possibility that Luwak would split one of my records across two blocks.