For information on exhibition and sponsorship opportunities at RailsConf, contact Yvonne Romaine at email@example.com.
Download the RailsConf Sponsor/Exhibitor Prospectus
View a complete list of RailsConf contacts.
Applications are strange things once they are in production. People use them and your data grows in size and complexity. Eventually a point is reached where the database can’t keep up and other layers are added. Sometimes it’s caching, other times it’s some kind of full-text indexing. After a few iterations of dealing with growth, applications can end up with multiple persistence layers. It can get messy.
We usually start our applications with a relational database and move on to more interesting problems. But where do you go from there? Is it better to make the leap to a document database, add caching, apply full-text indexing, or something else? What libraries are out there for growing our application? Should we go NoSQL, stick with SQL, or go with an unholy hodgepodge of storage systems? How do we deploy and monitor our new hotness?
In this talk, we’ll look at how to choose between caches, key-value stores, document databases, full-text indexes, and distributed databases. We’ll think about how to integrate these with our existing models and what kinds of libraries we might want to use. Finally, we’ll examine the tools and processes to operate our new systems in production.
Adam Keys is a software developer, entertainer and lover of animals. He works at Gowalla, reads a lot, and enjoys cracking wise.
Comments on this page are now closed.