Using memcached in front of a database gives me the best of both worlds

This was kind of how I thought memcached fit best with OtoDB. As the code currently stands, you will only be able to add a certain number of data servers before querying them all incrementally will prove a bottleneck (at least if my intuition doesn't fail me here). memcached is the obvious choice to keep queries frosty as you add more servers.

Also, to go along with your other point, an RDBMS also makes it easy to rebalance data, e.g. if you add new servers to a set of existing servers, and want to move some of the load over.

A blog among millions.

In reply to Re^3: RFC: OtoDB and rolling your own scalable datastore by arbingersys
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.