From everything I've been able to gather, general rule of thumb:
- Backbone is optimized for integrating with RESTful back ends
- Spine is optimized for local storage
It's not that you can't integrate spine with a back end, but it is focused on immediate actions so it'll show the item deleted before the server confirms that it is - leaving you with a UI conundrum if the delete fails some kind of business rule constraint.
Most tutorials for spine are "shopping cart" style local persistence examples and for that use case I think spine is slicker than backbone. Backbone integrates with RESTful services out of the gate though.
I like both frameworks, but I'd thoroughly recommend backbone for integrating with a rails back end. The Thoughbot team have even written a "Backbone with rails" ebook providing a good hands on tutorial
Best Wishes,