On Sat, Jul 10, 2010 at 10:33 AM, Marty Greenia <martygree...@gmail.com> wrote: > It almost seems counter-intuitive. For analytics, you'd think they'd want a > database that supports more sophisticated query functionality (sql). Whereas > for everyday tweet storage, something fast and high-throughput (cassandra) > makes sense. > > I'd be curious to here the details as well.
These decisions aren't made in a vacuum. One of these use cases has an existing system that works, one doesn't. -ryan
