http://www.dbms2.com/2010/06/30/details-and-analysis-of-the-voltdb-argument/ Choices in data management and analysis Thu, 09 Feb 2012 16:57:09 +0000 hourly 1 http://wordpress.org/?v=3.0.3 http://www.dbms2.com/2010/06/30/details-and-analysis-of-the-voltdb-argument/#comment-231947 An odd claim attributed to Mike Stonebraker | DBMS 2 : DataBase Management System Services Thu, 14 Jul 2011 11:10:39 +0000 http://www.dbms2.com/?p=2432#comment-231947 [...] week, Mike Stonebraker insulted MySQL and Facebook’s use of it, by implication advocating VoltDB instead. Kerfuffle ensued. To the extent Mike was saying that non-transparently sharded MySQL [...] [...] week, Mike Stonebraker insulted MySQL and Facebook’s use of it, by implication advocating VoltDB instead. Kerfuffle ensued. To the extent Mike was saying that non-transparently sharded MySQL [...]

]]> http://www.dbms2.com/2010/06/30/details-and-analysis-of-the-voltdb-argument/#comment-223699 Traditional databases will eventually wind up in RAM | DBMS 2 : DataBase Management System Services Tue, 24 May 2011 06:41:15 +0000 http://www.dbms2.com/?p=2432#comment-223699 [...] opinions at this time about marketing strategies or momentum at Oracle TimesTen, IBM solidDB, or VoltDB, but those examples at least serve to illustrate that memory-centric OLTP DBMS have existed for [...] [...] opinions at this time about marketing strategies or momentum at Oracle TimesTen, IBM solidDB, or VoltDB, but those examples at least serve to illustrate that memory-centric OLTP DBMS have existed for [...]

]]>