SQL v No SQL

transcript

SQL v No-SQLThe Great Debate

Open SQL Camp - Portland 2009 http://opensqlcamp.org #opensqlcamp

The Blue "SQL" Team

Ds Brian Aker (Drizzle)Js JD Duncan (MySQL)Mas Monty Widenius (MariaDB / ODBA)Ps Selena Deckelmann (PostgreSQL) Others: SQLLite, Ingres, Firebird

The Red "no-SQL" Team

Can Eric Evans (Cassandra)Hn Joydeep Sen Sarma (Hadoop / Hive) Mn Mike Dirolf (MongoDB)Con Mike Miller (CouchDB) Others: GAE,SimpleDB,Tokyo,Redis,LucidDB,MonetDB etc

The Blue Team

SQL Rules

The Red Team

SQL is dead

The Rules of Engagement

For each question: (5 minutes)

First team has 2 minutes Second team has 2 minutes to respond First team has a 1 minute rebutalAudience decides the winner of the question

When the timer ends, talking ends. Bribes are encouraged.Hawkers and heckling are allowed.

Audience Contributions

Please submit your questions via Twitter #opensqlcamp #greatdebate

Question 1:

SQL is a standard that most developers know, and most open source relational databases implement in a consistent manner.

How are the no-SQL offerings going to provide a more consistent and productive for software developers?

What benefits are there for not using SQL in development?

Brian Aker is not allowed to re-use Lightning talk material.

Question 2:

SQL databases have many open source products and offerings available via the LAMP stack, including popular blogging, wiki and Content Management (CMS) software (for example Wordpress, Drupal, Mediawiki etc ) With the newer non relational products now available what is the ideal industry segment or products (new and proposed) that will be of benefit for every day people?

What products won't work with no-SQL technologies?

Question 3:

Scalability and high availability with relational databases can really suck. This requires a great amount of planning and architecture to implement successfully in large scale environments. What are the strengths you can offer towards the needs for read scalability, write scalability, software upgrades and database maintenance without impacting the user experience?

Question 4:

Transactions form an essential component in many business critical systems including financial and military. How does my bank balance work in an eventually consistent environment?While many systems can survive without the need of database centric consistency, many developers need greater education.

How do you educate them for what is best?

Question 5:

From the audience

Question 6:

From the audience

Question 7:

Can SQL and noSQL co-exist happily in one software product offering? Can one be used as meta data or caching for the other?Is data interchangable?

Are there any benefits of working together?Are there any arguments for never working together?

Question 8:

A great product with a great code base can easily go the way of the dodo if there is not a supportive and active community.

What are each product group doing to better gain, retain and utilize the community for maximum benefit?

What do you do that other products should?What do other products do that you wish you did?

Question 9:

From the audience

Question 10:

From the audience

Wrap-up

SQL and no-SQL are really poor descriptions

Relational and non relational.

Is RDBMS and AltDB a better description.

Blended Solutions

e.g. Calpont/InfiniDB

RDBMS SQL interfaceColumn Oriented storageDirect non-SQL access to data as well

Blended Solutions

e.g. mod_ndb

json interface via apache to NDB Clustercan still use SQL synchronous scalable database

Blended Solutions

e.g. drizzle pluggable approach

gearmandistributed processingmap/reduce capabilities

memcached

SQL v No SQL

Technology