High Volume Transaction Processing Without Concurrency Control, Two Phase Commit, SQL or C++

@inproceedings{kdb-in-memory, abstract = {Imagine an application environment in which subsecond response to thousands of events gives the user a distinct competitive advantage, yet transactional guarantees are important. Imagine also that the data fits comfortably into a few gigabytes of Random Access Memory. These attributes characterize many financial trading applications. Which engine should one use in such a case? IBM FastPath, Sybase, Oracle, or Object Store? We argue that an unconventional approach is called for: we use a...}, author = {Whitney, Arthur and Shasha, Dennis and Apter, Stevan }, booktitle = {Int. Workshop on High Performance Transaction Systems}, citeulike-article-id = {2827958}, keywords = {concurrency-control, databases, in-memory-databases}, posted-at = {2008-05-24 18:10:04}, priority = {0}, title = {High Volume Transaction Processing Without Concurrency Control, Two Phase Commit, SQL or C++}, url = {http://citeseer.ist.psu.edu/6926.html} }

TY - CONF ID - kdb-in-memory L3 - citeulike-article-id:2827958 TI - High Volume Transaction Processing Without Concurrency Control, Two Phase Commit, SQL or C++ T2 - Int. Workshop on High Performance Transaction Systems N2 - Imagine an application environment in which subsecond response to thousands of events gives the user a distinct competitive advantage, yet transactional guarantees are important. Imagine also that the data fits comfortably into a few gigabytes of Random Access Memory. These attributes characterize many financial trading applications. Which engine should one use in such a case? IBM FastPath, Sybase, Oracle, or Object Store? We argue that an unconventional approach is called for: we use a... KW - concurrency-control KW - databases KW - in-memory-databases AU - Whitney, Arthur AU - Shasha, Dennis AU - Apter, Stevan UR - http://citeseer.ist.psu.edu/6926.html ER -