# A quick primer on sharding for Ruby on Rails - http://bit.ly/15k7Te

**URL:** <https://www.ruby-forum.com/t/a-quick-primer-on-sharding-for-ruby-on-rails-http-bit-ly-15k7te/170547>\
**Category:** Rails\
**Created:** [June 18, 2009, 7:09pm UTC](https://www.ruby-forum.com/t/a-quick-primer-on-sharding-for-ruby-on-rails-http-bit-ly-15k7te/170547 "2009-06-18T19:09:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![LJMecca](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/f475e1/32.png) [@LJMecca](https://www.ruby-forum.com/u/LJMecca)\
**Post date:** [June 18, 2009, 7:09pm UTC](https://www.ruby-forum.com/t/a-quick-primer-on-sharding-for-ruby-on-rails-http-bit-ly-15k7te/170547/1 "2009-06-18T19:09:47Z")

</div>

Sharding is usually the final strategy to reach for when scaling a  
Ruby on Rails application: caching, offloading, and data segmentation  
usually come before (they’re usually easier). Here’s info on Ruby on  
Rails application sharding, database sharding and filesystem sharding.  
[http://bit.ly/15k7Te](http://bit.ly/15k7Te)