We’d sincerely appreciate it if you could take some time to complete our first quarterly Riak community survey. The goal of this survey is to help us better understand how you are using Riak. Our hope is that your insights will help us make better decisions moving forward with the future of Riak.
All contributors to the survey will be provided Basho swag, as well as a discount for RICON tickets. One lucky contributor will be pseudorandomly selected to receive a free ticket to RICON | East!
If you have any questions or concerns, please don’t hesitate to hit up firstname.lastname@example.org.
November 4, 2012
For those of you not familiar with Riak Core, it’s more-or-less the distributed systems infrastructure that makes up, well, the core of how Riak distributes data and scales. For some introductory reading (that’s not pure code), there’s an old but still valuable blog post on the Basho Blog that’s well worth your time.
Why a separate list? Because Core is a powerful library that can be (and is being) used to build applications distinct of the other OTP apps (kv, search, pipe, etc.) that make up Riak. I know of at least 10 companies that have Riak Core apps in production, and I’m sure there are many more just waiting to share their use cases with the
world (hint hint…). Plenty of Riak issues are Core-related, and these should still be handled on the Riak Mailing List. However, as Core gets more use, there are questions, comments, and concerns that will be specific to Core, so a separate forum for these makes sense. There will be some overlap, too, and Basho will take responsibility for cross-posting when necessary.
We’ve long been convinced of the power of Core, but it has received less tooling (docs, tutorials, etc.) due to lack of engineering time. This is a great first step to helping put more community power and focus behind Core.
July 6, 2012
I’m excited to announce that v0.4 of the Riak Community Release Notes are official, covering what happened in the Riak Community from approximately June 1 thru June 30. Some highlights include:
- Matt Ranney and Ryan Sokol discussed Riak in Production at Voxer.
- Sean Cribbs gave a talk on CRDT’s at Berlin Buzzwords.
- The inaugural Paris Riak Meetup was held.
- The team at Near Infinity wrote a good introduction to Riak.
The community also shipped a bunch of code during the month of June, so if you have a few minutes read what else the Riak Community accomplished. Also, we’re already rolling with the 0.5 Release Notes (which will cover July 2 up through August 1). You’re encouraged to contribute to past, present, and future release notes, so don’t hold back.
Enjoy, and thanks for being a part of Riak.
June 4, 2012
I’m thrilled to announce that the v0.3 Riak Community Release Notes are now official. (For some history on the Community Release Notes, go here.) This installment covers what happened in the community from (approximately) May 4 through June 1. Some of the many stand-out accomplishments from this release:
- The team at Kiip gave a great talk on moving from MongoDB to Riak.
- Long-time Riak and Riak Search users and contributors Cliboard officially launched.
- The first Riak London Meetup was held.
- Mathias Meyer shipped a huge update to the Riak Handbook.
- Matt Ranney and the team at Voxer released their Node.js client for Riak.
We did a lot more. Take a few minutes to read up. Also, we’re already rolling with the 0.4 Release Notes (which will cover June 2 up through July 1). You’re encouraged to contribute to past, present, and future release notes, so don’t hold back.
Enjoy, and thanks for being a part of Riak.
May 9, 2012
Today I am excited to introduce a new piece of infrastructure to the Riak Community on which we’ve been working: Riak Community Release Notes.
Much like codebases grow and evolve, so does a community and its accomplishments. Why not present and chronicle the community in the same way you would a piece of code? The Riak Community Release Notes are an attempt to do just that.
Each month, we’ll tag and release a new “version” of the Riak Community. The most recent (and first official) release is v0.2. Each release will represent the evolution of the Community as demonstrated by our collective work and activity. For example:
- There were more than 20 blog posts about Riak in April
- Some of our users raised funding and welcomed new children to their family
- We released some (but not enough) new documentation.
My hope is that this will grow into a collaborative effort to track the trajectory of Riak and our user community. It looks somewhat like the Riak Recap, but I think it’ll extend and surpass it in a lot of ways. Most importantly, it’s an experiment, and I’m looking forward to how it evolves. Pull requests, feedback, and criticisms are welcomed.
Thanks for being a part of Riak.
March 26, 2012
This is a big week for Basho.
The first three days of Erlang Factory are primarily workshops, and Daniel Reverri will be teaching a 3 day class on Building Distributed Clusters with Riak. All attendees will walk away with a clear understanding of exactly why Riak is the best distributed database you will ever run in production.>
The actual conference spans Thursday – Friday, and the talk lineup for this year’s event is exceptional. The Basho team will be well-represented. Put these talks on your calendar if you’re attending:
- Test-First Construction of Distributed Systems – Joseph Blomstedt
- Building Healthy Distributed Systems – Mark Phillips
- Building Cloud Storage Services with Riak – Andy Gross
Several members of the Riak Community are also on the schedule:
- Erlang for .NET Developers – OJ Reeves
- Rewriting GitHub Pages with Riak Core, Riak KV, and Webmachine – Jesse Newland
Basho Bash West
We’re really excited about all the success surrounding Riak in 2011 and we’re continuously building on that momentum as we move deeper into 2012. The number of Riak users and community members are growing exponentially so we decided to throw a party to celebrate. We’re calling it Basho Bash West 2012, and it’s co-sponsored by our friends at Joyent, Yammer and Voxer.
Come join us on Thursday, March 29th, at 6:30PM. We are renting out Roe, and you won’t be allowed to pay for anything. You’ll also be leaving with some limited edition Riak swag that will make you the envy of all your friends. Various members of the Basho team will be in attendance, along with hundreds of developers, executives, and technology enthusiasts from the Bay Area. Miss this at your peril.
You must RSVP to attend.
May 26, 2011
Eric has been active in the Riak community for some time now, and, in addition to the numerous patches and bug fixes he has contributed to the Riak Python client, he’s also gone out of his way to help educate new and existing users about all things Riak on the Mailing List and in #riak on Freenode.
Make sure to keep an eye on the Riak Wiki Repo for his commits.
March 4, 2011
Anyone can contribute to the Riak Wiki: it’s maintained and deployed from a public GitHub repository, so everyone is free to fork and send us a pull request to make changes. There is, however, a group of community members who are given commit access to this repo, and I’m pleased to announce that Ryan Zezeski is now part of this group.
Ryan first became involved with Riak several months ago when he selected it as the production data store for a component of the ad-serving platform he works on during the daytime hours. Since then he has become an active and visible member of our community, contributing numerous patches to Luwak and providing guidance to new and existing users on the Riak Mailing list and in the Riak IRC Channel. In short, he knows his Riak and we are thrilled to have him on board as a Community Committer.
Welcome, Ryan! We are looking forward to your contributions.
December 16, 2010
The community contributions to Riak have been increasing at an exciting rate. The pull requests are starting to roll in, and I wanted to take a moment and recognize several of the many contributions we’ve received over the past months and weeks (and days).
Anyone who uses Riak with Ruby knows about Ripple. This is Basho’s canonical Ruby driver and its development has been spearheaded by Basho hacker Sean Cribbs. Not long after Sean started developing this code, he saw a significant influx in Rubyists who were interested in using Riak with Ruby and wanted to lend a hand in the driver’s development. Sean was happy to oblige and, as a result, there are now 15 developers in addition to Sean who have contributed to Ripple in a significant way. Special recognition should also be given to Duff Omelia and Adam Hunter who have made significant contributions to the code and use it in production.
Francisco Treacy and the team at Widescript made it known many months ago that they were looking into Riak to power part of their application. They, along with several other community members, were experimenting with Riak and Node.js. There were a few Node clients for Riak, but they were primarily experimental and immature. Basho had plans to write one but development time was stretched and a node client was several months off.
So, they rolled their own. Francisco, along with Alexander Sicular, James Sadler, Jakub Stastny, and Rick Olson developed and released riak-js. Since its release, it has picked up a ton of users and is being used in applications all over the place. (We liked it so much we even decided to build an app on it… more on this later.).
Thanks, guys, for the node client and helping to kickstart the Riak+Node.js community.
Riak Support in Spring Data
VMware’s Spring Data project is an ambitious one, and it has huge implications for the proliferation of new database technologies in application stacks everywhere. VMware made it known that Riak was slated for integration, needing only someone to take the time to write the code to connect the two. Jon Brisbin took up the task and never looked back.
Jon’s twitter stream is essentially a running narrative of how his work on Riak developed and, as you can see, it took about a month to build support for Riak into the Grails framework, the culmination of which was the 1.0.0.M1 release of the Riak Support in Spring Data.
So, if you’re using Riak with Spring Data, you have Jon Brisbin to thank for the code that made it possible. Thanks, Jon.
I met Daniel Lindsley at StrangeLoop in October. Rusty Klophaus and I were helping him debug a somewhat punishing benchmarking test he was running against a three node Riak cluster on his laptop (during a Cassandra talk) using Basho’s Python client. About a month later Daniel wrote a fantastic blog post called Getting Started With Riak & Python. Though his impressions of Riak were positive on the whole, one of the main points of pain for Daniel was that the Python library had poor documentation. At the time, this was true. Though the library was quite mature as far as functionality goes, the docs had been neglected. I got in touch with Daniel, thanked him for the post, and let him know we were working on the docs. He mentioned he would take a stab at updating the docs if he had a free moment. Shortly thereafter Daniel sent over a huge pull request. He rewrote all of the Python documentation! And it’s beautiful. Check them out here.
Thanks to Daniel and the rest of the team at Pragmatic Badger, we have robust Python documentation. Thanks for the contribution.
Want to contribute to Riak? There is still much code to be written and the Riak community is a great place to work and play. Download the code, join us on IRC, or take a look at GitHub repos to get started.
September 1, 2010
We added a new Community Editor this week. His name is Mårten Gustafson.
Aside from being involved in putting a Riak application into production, Mårten has been active, knowledgeable and helpful on the Riak Mailing list and in the IRC Room (where he goes by the unassuming “chids”). He recently came forward and expressed interest in being a Community Editor, and based on his Riak credentials, the team here at Basho was more than happy to bring him aboard.
Welcome, Mårten! We are looking forward to your contributions.
If you’re interested in being a Community Editor for the Riak Wiki, let us know. We would love to talk to you.