June 11, 2013
Mobile platforms and applications need to provide low-latency user experiences that can scale quickly and support highly concurrent user access. That is why so many mobile applications have selected Riak to handle their data.
To see if Riak is a fit for your mobile use case, we have put together a number of resources that showcase how mobile companies are using Riak to solve a variety of challenges. Below are some highlights:
- The “Mobile on Riak” whitepaper provides a technical introduction of Riak, specifically for mobile needs.
- Voxer has both a case study and a video that look at how they use Riak to support their massive, sudden growth.
- Bump, one of the most popular mobile apps, has a case study that looks at why they chose Riak to store their user data, and a video that goes into more details about their data model.
- Comcast uses Riak as the primary datastore for their “Highly-Available Object Storage System,” which is used by their mobile applications and websites. More details can be found in their case study and from their talk at RICON 2012.
- OmniTI uses Riak to power the mobile rewards provider, Viggle.
- On our blog, there are posts on the advantages of Riak for mobile and how to build mobile applications with Riak.
For a complete list of resources, visit our Resources Page.
June 4, 2013
If you’re interested in learning more about Riak, tune in this Friday, June 7th at 11am PT/2pm ET for an Intro to Riak webcast. You can sign up for this 30-minute webcast here.
This webcast will cover:
- Riak’s architecture, properties, and principles
- How to build apps with Riak’s key/value data model
- APIs and client libraries
- Deploying Riak in the cloud with AWS, Engine Yard, Azure, and more
- Common use cases for a variety of industries including advertising, retail, and mobile
- Case studies from users such as Copious, Yammer, Voxer, and OpenX
We will also be available after the webcast to answer any questions that you might have. You can register for the Intro to Riak webcast here.
March 25, 2013
We have a few new pages on our site to help you start building retail, advertising, mobile, or gaming apps and services on Riak. On each of these pages, you will find industry use cases for Riak, relevant case studies from companies already using it in production, and information on Riak’s key/value model and querying features. Here’s a quick overview:
Riak lets retailers provide always-on, highly scalable eCommerce and mobile services. Retail use cases for Riak include:
- Shopping carts
- Product catalogs
- Mobile applications/sites
Advertisers need to serve data reliably and quickly. Common ways advertisers leverage Riak include:
- Serving ad content
- Session storage
- Mobile experiences
Riak provides the scalable, small object storage required by mobile applications and platforms. Riak can be used for many different mobile needs, including:
- User and session data storage
- Text and multimedia storage
- Social authentication
Gaming platforms and applications benefit from Riak’s scale-out, low-latency design, and flexible storage capabilities. Some common use cases include:
- Player data
- Session data
- Social information
- Gaming assets
February 26, 2013
Mobile platforms and applications pose unique infrastructure challenges for today’s companies. These applications require low-latency, always-available small object storage that can scale to millions or more users, and support highly concurrent access and traffic spikes.
Riak provides a number of benefits for these platforms, including:
- Low-Latency Data Storage: Riak is designed to serve predictable, low-latency requests to provide a fast, available experience to all users.
- Straightforward Data Model: Riak uses a simple key-value data model, which is ideal for storing and serving mobile content, user information, events, and session data. Riak is content agnostic, so there are no restrictions on content type.
- Accommodates Peak Loads Gracefully: To handle increasing user data and accommodate peak loads during events, Riak makes it easy to add additional capacity and scale out quickly. Riak automatically rebalances data when new nodes are added, while its consistent hashing methodology prevents hot spots in the database.
- Multi-Datacenter Replication: Riak Enterprise’s multi-datacenter replication allows mobile platforms to serve low-latency content to users all over world by maintaining a global data footprint.
- For a full overview, download our new whitepaper on building mobile services with Riak
Bump is a popular mobile app that makes it easy for users to share their contact information, photos, and other objects by simply “bumping” their smartphones. They use Riak to store user data and currently run 25 nodes of Riak storing about 3TB of data.
For more details about how Bump uses Riak and how they designed their application, check out Bump’s presentation at RICON2012, Basho’s 2012 developer conference. You can also read the complete case study for more information about why Bump chose Riak.
Voxer is a popular Walkie Talkie application for smartphones that allows users to send instant voice messages to one or more friends. They switched to Riak due to its fault-tolerance and ability to scale quickly and easily. They currently run more than 50 machines on Riak to support their huge growth and user base. For more details about how Voxer uses Riak, check out the complete case study and watch Matt Ranney’s talk at a Riak Meetup in San Francisco.
To learn more about how mobile platforms can use Riak for their data needs, check out the complete overview, “Mobile on Riak: A Technical Introduction.”
June 27, 2012
The team at Voxer has long relied on Riak as their primary data store for various production services. Over the last year or so, they have put Riak through its paces and have served as one of our more exciting customers and use cases: Riak was in place when they shot to the top of the App Store at the end of last year. We also love them because they open-sourced their Node.js client for Riak about a month back.
This talk was recorded last week at the Riak Meetup in San Francisco. In it, Matt Ranney, CTO, and Ryan Sokol, Director of Engineering, go in depth on why they selected Riak over a few other databases, how they built their services on it, the issues they ran into in production (and where they think Riak should improve) and, ultimately, why they feel Riak is the only technology capable of supporting their massive growth over the past twelve months. It’s an all-around great talk full of honest feedback and experience from one of our largest production users.
A few things to note:
* Their slides are here for those of you who like PDFs.
* Matt references this blog post about TCP Incast about halfway through the talk.
* If you want to work with Voxer on systems like this, they are hiring (and, in addition to having a great team, their new SF office is downright amazing).
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 14, 2012
I’m excited to announce that Matt Ranney and the team at Voxer just open-sourced their production Node.js client for Riak, node_riak. Voxer has been using this code in production for months now, and it has been battle-tested with Riak clusters doing billions of requests daily and that are storing on the order of 100s of terabytes of raw data.
In addition to more code, Matt and his team will be working to add documentation and other resources to the repo as time allows. Interested parties are encouraged to fork, use, and contribute.
Enjoy, and thanks again to Matt and his team for releasing the library. Here’s the link to the repo once more: node_riak
Also, if you want to work with Riak, Node.js, and other technologies that power Voxer, check out their job listings. You won’t be disappointed.