On Oct 6, 2012, at 2:36 PM, Guyren Howe wrote: > On Oct 6, 2012, at 2:34 PM, Thomaz Leite <[email protected]> wrote: > >> Reading this[1] article on High Scalability I found out Reddit has (or had >> at some point) only two tables in their database. It's an interesting >> approach to delay decisions about the schema, but I wonder if the drawbacks >> are worth it. What do you think? >> >> [1]: >> http://highscalability.com/blog/2010/5/17/7-lessons-learned-while-building-reddit-to-270-million-page.html > > I think I’d be inclined to have at least some of the application using a > regular schema. The poor database has to do an awful lot of joins with this. > Still, clearly it works at least to some extent, and if you ran the thing out > of an SSD, the joins wouldn’t be such an issue. > > Note that you can get quite a lot of this kind of flexibility in Postgres > using Array and HStore field types, which I mentioned in a presentation a > couple of months back.
Some of the comments on the link point out that since then they have actually started using Cassandra, which I think makes sense for them: They were not using a RDBMS schema anyway, might as well go with a NoSQL solutions. I would be interested to know to what lengths they went to solve their schema migrations problems, before they went to a EAV model. -- Ylan. -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
