(2009-03-18) Friendfeed Schemaless Mysql

FriendFeed uses MySQL but with no schema. Our datastore stores Schema-Less bags of properties (e.g., JSON objects or Python dictionaries (Hash Table)). The only required property of stored entities is id, a 16-byte UUID. The rest of the entity is opaque as far as the datastore is concerned. We can change the "schema" simply by storing new properties. We index data in these entities by storing indexes in separate MySQL tables. If we want to index three properties in each entity, we will have three MySQL tables - one for each index. (Scalability)

Hmm, this reminds me of RDF Triple Store-s.

Edited:    |       |    Search Twitter for discussion