Storing images in a noSQL database might be a good approach for many applications, and it can alleviate many replication and scalability issues when it comes to images and by extension other binary files.
Riak can store any kind of data, including binary. Whatever you can turn into an Erlang tuple can be stored, without the 4MB document size limitation of MongoDB or the “attachment”-model of CouchDB.
First, ripple has to be installed, the “official” Ruby driver for Riak:
sudo gem install ripple
Then require it in environment.rb of your Rails app:
This gem will pull some dependencies, namely activesupport-3.x and also activemodel. To continue working with Rails 2.3.5 without these beta gems, first uninstall them:
sudo gem uninstall activesupport –version ’3.0.0.beta3′
sudo gem uninstall activemodel
You will now get
no such file to load — active_support/i18n
when trying to start the server.
Sean is in the process of splitting the ripple gem into the ‘riak’ and ‘ripple’ (OM) parts to make the ‘riak’ part compatible with Rails 2.3.5., but for now you could either unpack the gem into vendor/gems (Google is your friend), or patch the offending file (your path may be different):
By simply changing
Now script/console or script/server will still give a bunch of warnings but the app should start.
Finally, here’s the snippet to store an image in riak:
client = Riak::Client.new
bucket = client.bucket(“my_image_store”)
object = Riak::RObject.new(bucket, “elephant_in_room.jpg”)
object.content_type = “image/jpeg”
fi = File.new(“/path/to/elephant.jpg”, “r”)
object.data = fi
Now point your browser to
and there is your image, just as you read it from disk.
Note the structure of the URL
and behold the simplicity and predictability of an HTTP/REST API. Accessing data really becomes a “no-brainer”. Riak of course vastly expands on this concept with links.
Surely you’ll want to embed the image in a larger document but this snippet might help you to get started.