The case for shared nothing Export

@article{citeulike:3335639, abstract = {There are three dominent themes in building high transaction rate multiprocessor systems, namely shared memory (e.g. Synapse, IBM/AP configurations), shared disk (e.g. VAX/cluster, any multi-ported disk system), and shared nothing (e.g. Tandem, Tolerant). This paper argues that shared nothing is the preferred approach. 1.}, author = {Stonebraker, Michael}, citeulike-article-id = {3335639}, citeulike-linkout-0 = {http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.58.5370}, journal = {Database Engineering}, keywords = {4ref, architecture, classic, dbms, sharednothing}, pages = {4--9}, posted-at = {2008-11-12 16:46:18}, priority = {2}, title = {The case for shared nothing}, url = {http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.58.5370}, volume = {9}, year = {1986} }

TY - JOUR ID - citeulike:3335639 L3 - citeulike-article-id:3335639 N2 - There are three dominent themes in building high transaction rate multiprocessor systems, namely shared memory (e.g. Synapse, IBM/AP configurations), shared disk (e.g. VAX/cluster, any multi-ported disk system), and shared nothing (e.g. Tandem, Tolerant). This paper argues that shared nothing is the preferred approach. 1. JF - Database Engineering EP - 9 TI - The case for shared nothing VL - 9 SP - 4 KW - 4ref KW - architecture KW - classic KW - dbms KW - sharednothing AU - Stonebraker, Michael PY - 1986/// UR - http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.58.5370 ER -