Comments on: A super-set of MySQL for Big Data. Interview with John Busch, Schooner. http://www.odbms.org/blog/2012/02/a-super-set-of-mysql-for-big-data-interview-with-dr-john-busch-schooner/ Trends and Information on New Data Management Technologies, Innovation. Wed, 17 Apr 2013 21:47:18 +0000 hourly 1 http://wordpress.org/?v=3.1.1 By: Roberto V. Zicari http://www.odbms.org/blog/2012/02/a-super-set-of-mysql-for-big-data-interview-with-dr-john-busch-schooner/comment-page-1/#comment-7291 Roberto V. Zicari Wed, 29 Feb 2012 16:58:48 +0000 http://www.odbms.org/blog/?p=1333#comment-7291 Thank you Fred. Roberto Thank you Fred.

Roberto

]]> By: Fred Holahan http://www.odbms.org/blog/2012/02/a-super-set-of-mysql-for-big-data-interview-with-dr-john-busch-schooner/comment-page-1/#comment-7288 Fred Holahan Tue, 21 Feb 2012 14:59:01 +0000 http://www.odbms.org/blog/?p=1333#comment-7288 Roberto, thanks for the interesting post. While I'm sure SchoonerSQL is a fine product, Mr. Busch's comment - "superior cost of ownership and availability relative to VoltDB" - seem broad and uninformed. Under what workloads does SchoonerSQL offer superior TCO? All workloads? Including workloads that scale to millions of write operations per second? And how is TCO measured in this broad context? Cost of hardware and software? Including costs of set-up, management and infrastructure support, particularly in distributed deployments involving 3rd party products like DBShards? With regard to "superior" availability, what's the basis of this claim? How would Mr. Busch compare, in detail, VoltDB's synchronous multi-master HA solution to what SchoonerSQL provides (with and without DBShards) to conclude that Schooner's solution is superior in all database applications, as his statement suggests? Choosing the right database for one's application has never been more challenging, nor more critical. Like no time in the past, developers and data architects need guidance about when database solutions do and do not fit. Broad, uninformed comments, therefore, should be viewed with considerable scrutiny. Fred Roberto, thanks for the interesting post. While I’m sure SchoonerSQL is a fine product, Mr. Busch’s comment – “superior cost of ownership and availability relative to VoltDB” – seem broad and uninformed.

Under what workloads does SchoonerSQL offer superior TCO? All workloads? Including workloads that scale to millions of write operations per second? And how is TCO measured in this broad context? Cost of hardware and software? Including costs of set-up, management and infrastructure support, particularly in distributed deployments involving 3rd party products like DBShards?

With regard to “superior” availability, what’s the basis of this claim? How would Mr. Busch compare, in detail, VoltDB’s synchronous multi-master HA solution to what SchoonerSQL provides (with and without DBShards) to conclude that Schooner’s solution is superior in all database applications, as his statement suggests?

Choosing the right database for one’s application has never been more challenging, nor more critical. Like no time in the past, developers and data architects need guidance about when database solutions do and do not fit. Broad, uninformed comments, therefore, should be viewed with considerable scrutiny.

Fred

]]>