Joe Gregorio | BitWorking | ETech '07 Summary - Part 2 - MegaData - 0 views
-
the limits you need to put on yourself when storing a billion rows in a database, and they included: no joins, no transactions, no stored procedures, and no triggers.
-
Joshua has similar suggestions from his experience building del.icio.us: no joins, no transactions, no autoincrement
-
BigTable, Google's column-based store with no transactions
-
- ...4 more annotations...
-
What's the point in designing tables for a webapp when an RDF-backed store will manage the data for you and RDF queries will come back as tabular data anyway?
-
designing and maintaining yet another relational schema for yet another webapp - doing so is starting to make as much sense as designing my own filesystem or TP monitor.
-
RDF + SPARQL + distributed data sources from around the web?
-
reason that rails and django are so productive; they're highly optimised for domain models. Raw RDF doesn't really do domains like that; you have to expend effort distilling triples into 'things';
-
Database design for huge data. Distributed, joinless, transactionless, de-normalized database