This is an implementation of the ideas found in this article about how FriendFeed uses MySQL. You should read that article for all the details.
Turn MySQL in to a document db!
Why? Everybody is super excited about NoSQL. Aside from the ridiculous rumour that removing SQL makes things magically scalable, there's a lot of reason to look forward to these new data storage solutions.
One of the biggest improvements is where schema / index changes are concerned. When you have a ton of data, migrating MySQL tables takes forever and locks the table during the process. Document dbs like mongo and couch, on the other hand, are schemaless. You just add and remove fields as you need them.
But, the available document oriented solutions are still young. While many of them show great promise, they've all got their quirks. For all its flaws, MySQL is a rock. It's pretty fast, and battle-hardened. We never have problems with MySQL in production.
Fortunately, with a little extra work on the client-side, we can get the flexibility of a doc db in MySQL!
How it Works
Let's say we had a user model.
class User include Friendly::Document attribute :name, String attribute :age, Integer end
Friendly always stores your documents in a table with the same schema:
CREATE TABLE users ( added_id INT NOT NULL AUTO_INCREMENT PRIMARY KEY, id BINARY(16) NOT NULL, created_at DATETIME NOT NULL, updated_at DATETIME NOT NULL, attributes TEXT, UNIQUE KEY (id), ) ENGINE=InnoDB;
- added_id is there because InnoDB stores records on disk in sequential primary key order. Having recently inserted objects together on disk is usually a win.
- id is a UUID (instance of Friendly::UUID).
- created_at and updated_at are exactly what they sound like - automatically managed by Friendly.
- attributes is where all the attributes of your object are stored. They get serialized to json and stored in there.
We can instantiate and save our model like an ActiveRecord object.
@user = User.new :name => "James" @user.save
As is, our user model only supports queries by id.
User.find(id) User.first(:id => id) User.all(:id => [1,2,3])
Not great. We'd probably want to be able to query by name, at the very least.
To support richer queries, Friendly maintains its own indexes in separate tables. To index our user model on name, we'd create a table like this:
CREATE TABLE index_users_on_name ( name varchar(256) NOT NULL, id binary(16) NOT NULL, PRIMARY KEY (name, id) UNIQUE KEY unique_index_on_id (id) ) ENGINE=InnoDB DEFAULT CHARSET=latin1
Then, we'd tell friendly to maintain that index for us:
class User # ... snip ... indexes :name end
Any time friendly saves a user object, it will update the index as well. That way, we can query by name:
User.first(:name => "James") User.all(:name => ["James", "John", "Jonathan"])
One of the big advantages to this approach is that indexes can be built offline. If you need a new index, you can write a script to generate it in the background without affecting the running application. Then, once it's ready, you can start querying it.
Friendly has built-in support for write-through caching.
First, install the memcached gem:
sudo gem install memcached
Then, configure your cache:
$cache = Memcached.new # you'll probably want to pass some params here. Friendly.cache = Friendly::Memcached.new($cache)
Finally, declare the cache in your model:
class User # ... snip ... caches_by :id end
This tells Friendly to automatically write through to cache on save, and read through to the cache if it needs to hit the database on a query.
Currently, only caching by id is supported, but caching of arbitrary indexes is planned.
We're seeing a 99.8% cache hit rate in production with this code.
It's possible to create a scope that you can refer to by name:
class Post attribute :author, String named_scope :by_james, :author => "James" end
Calling the scope will provide you with a Friendly:Scope object:
Post.by_james #=> #<Friendly::Scope>
That scope object supports a variety of methods. Calling any of the methods is the equivalent of calling those methods directly on Document with the scope's parameters.
Post.by_james.all == Post.all(:author => "James") Post.by_james.first == Post.first(:author => "James") Post.by_james.paginate # => #<WillPaginate::Collection> Post.by_james.build.name == "James" @post = Post.by_james.create @post.new_record? # => false @post.name # => "James"
Each of the methods also accepts override parameters. The APIs are the same as on Document.
Post.by_james.all(:author => "Steve") == Post.all(:author => "Steve")
You can also compose arbitrary combinations of scopes with simple chaining.
class Post # ... snip ... named_scope :recent, :order! => :created_at.desc, :limit! => 4 indexes :name, :created_at end Post.by_james.recent == Post.all(:name => "James", :order! => :created_at.desc, :limit! => 4)
If two parameters conflict, the right-most scope takes precedence.
You can also create a scope object on the fly:
Post.scope(:author => "Steve")
The object you get is identical to the one you get from a named_scope. So, see above for the API.
Friendly currently only supports has_many associations.
Creating a has_many is as simple as setting up the necessary association and foreign key.
Note: Make sure that the target model is indexed on the foreign key. If it isn't, querying the association will raise Friendly::MissingIndex.
class Post attribute :user_id, Friendly::UUID indexes :user_id end class User has_many :posts end @user = User.create @post = @user.posts.create @user.posts.all == [@post] # => true
Friendly defaults the foreign key to class_name_id just like ActiveRecord. It also converts the name of the association to the name of the target class just like ActiveRecord does.
The biggest difference in semantics between Friendly's has_many and active_record's is that Friendly's just returns a Friendly::Scope object. If you want all the associated objects, you have to call #all to get them.
You can also use any other Friendly::Scope method like scope chaining.
# note: the Post.recent scope is defined in the above section @user.posts.recent == Post.all(:user_id => @user.id, :order! => :created_at.desc, :limit! => 4)
See the section above or the Friendly::Scope docs for more details.
Friendly includes support for building an index in the background, without taking your app offline.
All you have to do is declare the index in your model. If we wanted to add an index on :name, :created_at in a User model, we'd do it like this:
class User # ...snip... indexes :name, :created_at end
Then, make sure to run Friendly.create_tables! to create the table in the database. This won't overwrite any of your existing tables, so don't worry.
Now that the the new table has been created, you need to copy the .rake file included with Friendly (lib/tasks/friendly.rake) to somewhere that will get picked up by your main Rakefile (lib/tasks if it's a rails project). Then, run:
$ KLASS=User FIELDS=name,created_at rake friendly:build_index
If you're running this in production, you'll probably want to fire up GNU screen so that it'll keep running even if you lose your SSH connection. When this task completes, the index is populated and ready to go!
Friendly is available as a gem. Get it with:
sudo gem install friendly
All you have to do is supply Friendly with some information about your database:
Friendly.configure :adapter => "mysql", :host => "localhost", :user => "root", :password => "swordfish", :database => "friendly_development"
Now, you're ready to rock.
If you're using rails, set friendly as a gem dependency:
...and drop something like this in config/friendly.yml (an example of such a config exists in examples/friendly.yml):
development: :adapter: "mysql" :host: "localhost" :user: "root" :password: "swordfish" :database: "friendly_development"
Of course, you'll want to swap out these values for your own, fill in additional environments, and so forth.
Then, create some models, and run:
That'll create all the necessary tables as best it can. This has worked well enough for me, but it's possible that certain table configurations will fail. It won't attempt to create any tables that already exist, so it's safe to run in an initializer or something.
- Online migrations. Add a version column to each model and a DSL to update schema from one version to another on read. This facilitates data transformations on the fly. If you want to transform the whole table at once, just iterate over all the objects, and save.
- Offline indexer
- Caching of arbitrary indexes
- A lot more documentation
Friendly was developed by James Golick & Jonathan Palardy at FetLife (nsfw).
Copyright (c) 2009 James Golick. See LICENSE for details.
Except for friendly/uuid.rb which is copyright Evan Weaver and Apache Licensed. See APACHE-LICENSE for details.