in reply to Re: RFC: OtoDB and rolling your own scalable datastore
in thread RFC: OtoDB and rolling your own scalable datastore

One problem with memcached is that it is hard to take a backup of it. I love the product, but I also like my data to be a little safer than that. Using memcached in front of a database gives me the best of both worlds.

Another reason to use an RDBMS is that while your application may not take advantage of the relational structure, it is still there to be exported to and manipulated on reporting databases.

  • Comment on Re^2: RFC: OtoDB and rolling your own scalable datastore

Replies are listed 'Best First'.
Re^3: RFC: OtoDB and rolling your own scalable datastore
by arbingersys (Pilgrim) on Jul 15, 2008 at 04:02 UTC

    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.