RSS feed [root] /examples /design /weblog



title search:


Fri Nov 01 17:28:59 AEDT 2013


Key points

1) No stored procedures are used. There are some very simple triggers.
2) Move cpu-intensive work moved out of the database layer to applications applications layer: referential integrity, joins, sorting done in the application layer! Reasoning: app servers are cheap, databases are the bottleneck.
3) No client-side transactions. no distributed transactions
4) J2EE: use servlets, JDBC, connection pools (with rewrite). Not much else.
5) No state information in application tier. Transient state maintained in cookie or scratch database.

How ebay use Cassandra -[..]-practice-of-cassandra-data-model-design[..]ctices-cassandra-data-model-design-part2[..]dra-data-modeling-best-practices-part-1/[..]dra-data-modeling-best-practices-part-2/

(google search) (amazon search)
download zip of files only