We store data in a really similar way at Spock, pointing all our reads at a big MySQL table which essentially just has an id column and a really big text column containing all the values, JSON-encoded, w/roughly the same number of rows as the FriendFeed table. Our DBA wrote a blog post about it a while back: http://www.frankf.us/wp/?p=17
The way you guys create/delete indices and avoid all the replication nightmares sounds super cool.
All of these solutions ultimately end up sounding like a poor man's Big Table.
Comments
Thanks for sharing. That was very educational.
We store data in a really similar way at Spock, pointing all our reads at a big MySQL table which essentially just has an id column and a really big text column containing all the values, JSON-encoded, w/roughly the same number of rows as the FriendFeed table. Our DBA wrote a blog post about it a while back: http://www.frankf.us/wp/?p=17
The way you guys create/delete indices and avoid all the replication nightmares sounds super cool.
All of these solutions ultimately end up sounding like a poor man's Big Table.