This document discusses remodel, an ORM that maps Ruby objects to Redis to provide fast and scalable data storage. It highlights that remodel is faster than MySQL for read and write operations since it stores data in memory instead of disk. The document demonstrates remodel's features like associations and basic validations and notes its current alpha status and roadmap for improvements.

1. remodel
your persistence layer

2. ORM

3. object redis mapper

4. “People that are wrapping
ORM’s around redis are missing
the point.”
— Nate Wiger

5. OMG

6. why replace mysql
with remodel + redis ?

7. “Memory is the new Disk.
Disk is the new Tape.”
— Jim Gray

8. speed!
flickr.com/photos/atzu/2645776918

9. mysql
• read scaling
• vertical: more memory
• horizontal: master-slave replication
• write scaling
• vertical: more / faster disks (raid, ssd ...)
• horizontal: sharding

10. “You are not Facebook.” — me

11. redis
• ~ 100K ops / second (read or write)
• read scaling?
• probably not necessary
• write scaling
• probably not necessary
• (but sharding is possible)

12. remodel
• “minimal” object mapper
• mapping strategy:
• unique key prefix per entity class
• serialize properties to json
• store associations as separate keys
• less than 300 lines of ruby

13. features
• supports all basic ruby / json types
• plus custom mappers (date, time ...)
• associations
• one-to-many / many-to-one
• one-to-one, many-to-many

15. demo time!
flickr.com/photos/78918694@N00/3519713609

16. limitations
• only very basic validations
• use ActiveModel::Validations
• no complex finders
• not supported by redis
• maybe somebody wants to build
redis-lucene ?

17. roadmap
• current status — alpha (0.1.0)
• next month:
• “eat your own dogfood”
• bugfixing
• documentation
• beta release

18. ideas
• find_by(with ohm-like indexes)
• optimistic locking
• re-implement in node.js
• .... what else ?

19. ??

20. fork me:
github.com/tlossen
/remodel