opinion statements by an otherwise unimportant guy. Pictures are copyrighted by their respective owners. On Database History and NoSQL Studied all the different *SQL-Systems out there. Still having data issues. (Dr. Faustus)
opinion statements by an otherwise unimportant guy. Pictures are copyrighted by their respective owners. On Database History and NoSQL Studied all the different *SQL-Systems out there. Still having data issues. (Dr. Faustus) I am the spirit that denies NoSQL. (Mephisto. That’s me.)
NoSQL land! • No (simple) way to ensure various quality domains of data • timeliness and appropriateness • correctness and consistency • Data Integration and Data Quality assurance becomes a full-stack concern!
• sporting 19.5m update transactions per second[1] • yet, it’s Oracle and we all know its a benchmark business. [1] http://mikaelronstrom.blogspot.co.uk/2012/05/mysql-cluster-727-achieves-1bn-update.html
interface between programs and files” • Separation and Isolation: Every program has its own files and formats • Duplication, Synchronization, Consistency: Programs share data. Data is not necessarily synchronized or in a consistent state. • Weak Security, High maintenance Costs http://www.comphist.org/computing_history/new_page_9.htm
(Cassandra, HBase, Riak, etc.) Separation & Isolation Duplication, Synchronization, Consistency, Security, Maintenance Costs Every program has its own files and formats Every Data Store has its own APIs and Data Models Programs share data. Data not necessarily consistent, synchronized or consistent Content Transferred into Hadoop. Limited consistency by data model Almost no security; manual data processes Almost no security; Specialized personnel required
of Data for Large Shared Data Banks” • Father of Relational Database Management Systems • Basically invented what Twitter and FB run on • Now a +$12B business • we owe him more than an applause.
Separate Logical Data Model from Physical Data Storage • Radical Simplification of Data Access • A phenomenal tool was introduced: Joins • great for “single data insert, multiple views of data”
HBase, Riak, etc.) Logical & Physical Data Model Duplication, Synchronization, Consistency, Downsides Separated Complected Normalization; Constraints for improved data quality Denormalization; Data Quality an Application- level Problem Scalability Issues; some DBMSs quite expensive Almost no security; Specialized personnel required
Databases over Files 1980 It’s Minicomputers all over Software becomes a product Relational DBMS + SQL It’s Cloud Computing all over Software becomes a Service 2012
Databases over Files 1980 It’s Minicomputers all over Software becomes a product Relational DBMS + SQL It’s Cloud Computing all over Software becomes a Service NoSQL? 2012
Databases over Files 1980 It’s Minicomputers all over Software becomes a product Relational DBMS + SQL It’s Cloud Computing all over Software becomes a Service NoSQL? 2012 So far: Every HW iteration a new DB Technology Is Cloud Computing a backlash? Will NoSQL prevail?
storage and transactional access is solved. Everybody can (soon) rent the perfect data storage system in the cloud. • Issue #1: Data-Integration an open task • Issue #2: Data-Quality an open task • Issue #3: Push-based execution model: where are thou?
storage and transactional access is solved. Everybody can rent the perfect data storage system in the cloud. • Issue #1: Data-Integration an open task • Issue #2: Data-Quality an open task • Issue #3: Push-based execution model: where are thou? • The new competitive frontier: Timeliness, Data Integration and Quality
NoSQL will become yet another DB Feature and/or Cloud Computing Service. PostSQL Databases will be indistinguishable from Data Communication Services. Claim #3:
NoSQL will become yet another DB Feature and/or Cloud Computing Service. PostSQL Databases will be indistinguishable from Data Communication Services. Claim #3: