Well, if you like ActiveRecord and SimpleDB (aws), I recommend http://github.com/appoxy/simple_record
However, and I don't mean this to inflame anyone, but ActiveRecord may fundamentally oppose NoSQL - while ActiveRecord makes joins easy (for the programmer, not so much for the db), those joins don't scale well. [To other people's points, a single MySQL can take you a very long way with minimal joins and good row-level caching.] The NoSQL way is to get (minimal) results from a single table at a time, then if necessary, do other queries to get connected data. In other words, instead of sending joined queries to the db layer, you unwrap (efficiently) them in your code. marc -- getCloudCache.com On Wed, Mar 24, 2010 at 5:13 PM, brianp <brian.o.pea...@gmail.com> wrote: > > > On Mar 24, 4:59 pm, Marc Byrd <dr.marc.b...@gmail.com> wrote: > > Life may be much simpler for you when you scale if you use a nosql > option, > > What nonsql option would you recommend? > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to rubyonrails-t...@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscr...@googlegroups.com<rubyonrails-talk%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
