You're not going to get 65k queries per second out of an RDBMS if any of those queries have to do JOINs, and you're not going to put Varnish in front of it to speed it up even further. You can do that with memcached and CouchDB, for example.

I'm by no means suggesting that there's anything wrong with JOIN, or that every persistent data storage needs to do what eBay or MySpace or Amazon.com does. Yet by the time your problem is that your database is a bottleneck, slapping something on top of the database doesn't seem like the right approach.

(Similarly, I have the strong belief that if ActiveRecord could run on something other than an RDBMS, everyone would be a lot happier.)

In reply to Re^3: RFC: OtoDB and rolling your own scalable datastore by chromatic
in thread RFC: OtoDB and rolling your own scalable datastore by arbingersys

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.