This document discusses SQL vs NoSQL databases. It provides definitions of NoSQL, highlighting that it refers to non-relational databases. The main differences between SQL and NoSQL are that NoSQL databases are better for scaling across servers and do not require predefined data models. The document also discusses various data structures used in NoSQL and considerations around structured vs unstructured data. It raises the question of whether OSEHRA should use SQL or NoSQL for its data persistence layer given needs like multiple EHR systems, data stores, cloud architecture and flexible data models.
This document discusses SQL vs NoSQL databases. It provides definitions of NoSQL, highlighting that it refers to non-relational databases. The main differences between SQL and NoSQL are that NoSQL databases are better for scaling across servers and do not require predefined data models. The document also discusses various data structures used in NoSQL and considerations around structured vs unstructured data. It raises the question of whether OSEHRA should use SQL or NoSQL for its data persistence layer given needs like multiple EHR systems, data stores, cloud architecture and flexible data models.
This document discusses SQL vs NoSQL databases. It provides definitions of NoSQL, highlighting that it refers to non-relational databases. The main differences between SQL and NoSQL are that NoSQL databases are better for scaling across servers and do not require predefined data models. The document also discusses various data structures used in NoSQL and considerations around structured vs unstructured data. It raises the question of whether OSEHRA should use SQL or NoSQL for its data persistence layer given needs like multiple EHR systems, data stores, cloud architecture and flexible data models.
This document discusses SQL vs NoSQL databases. It provides definitions of NoSQL, highlighting that it refers to non-relational databases. The main differences between SQL and NoSQL are that NoSQL databases are better for scaling across servers and do not require predefined data models. The document also discusses various data structures used in NoSQL and considerations around structured vs unstructured data. It raises the question of whether OSEHRA should use SQL or NoSQL for its data persistence layer given needs like multiple EHR systems, data stores, cloud architecture and flexible data models.
Download as PPT, PDF, TXT or read online from Scribd
Download as ppt, pdf, or txt
You are on page 1of 9
SQL vs NOSQL Discussion
OSEHRA Architecture Working Group
July 3, 2012 SQL vs NOSQL AGENDA • What is NOSQL? • How does NOSQL compare to SQL? • Data structures and performance considerations • Why should OSEHRA care about SQL vs NOSQL?
OSEHRA AWG SQL vs NOSQL Discussion July 3, 2012
What is NOSQL? • NoSQL is a class of database management system identified by its non-adherence to the widely used relational database management system (RDBMS) model with its structured query language (SQL). • NOSQL has evolved to mean “Not Only” SQL • NOSQL has become prominent with the advent of web scale data and systems created by Google, Facebook, Amazon, Twitter and others to manage data for which SQL was not the best fit.
OSEHRA AWG SQL vs NOSQL Discussion July 3, 2012
What is NOSQL? • Definitions for NOSQL vary greatly from newer systems using document stores, key value stores, XML databases, graph databases, column stores, object stores, etc. (like MongoDB, Cassandra, Couchbase, Hadoop, etc.) to older Hierarchical systems that had many similar characteristics (like Cache and GT.M) • The NOSQL concept tree illustrates the variety of concepts related to NOSQL. NOSQL Concept Tree Source: CIO’s Guide to NOSQL, Dan McCreary, June 2012
How Does NOSQL compare to SQL? While there are numerous characteristics that differentiate SQL and NOSQL the two most significant are Scaling and Modeling. • Scaling – Traditionally SQL does not lend itself to massively parallel processing, which lead to larger computers (scale up) vs. distribution to numerous commodity servers, virtual machines or cloud instances (scale out).
• Modeling – SQL databases are highly normalized and require pre-
defined data models prior to inserting data into the system. In contrast NOSQL databases do not require (although they support) pre-defined data model(s).
OSEHRA AWG SQL vs NOSQL Discussion July 3, 2012
Data structures and performance considerations • Structured vs. Unstructured – Tables, fields, pairs vs. unstructured text • Transactions vs. Analytics • Federated vs. Persisted • Big Data: Volume, Variety and Velocity • Retrieval – Indexing, MapReduce, Search, Query • Precision vs. Discovery
OSEHRA AWG SQL vs NOSQL Discussion July 3, 2012
Why should OSEHRA care about SQL vs NOSQL? • Multiple EHR’s and EHR instances with different data models (VistA, CHCS, AHLTA, Epic, Cerner, etc.) • Multiple data stores (VistA CDW, VistA HDR, AHLTA CDR, etc.) • Semantic interoperability (3M HDD, SNOMED, LOINC, HL7, ICD 9 & 10, RxNorm, CPT, etc.), metadata and master data management (EMPI, providers, organizations, locations, devices, etc.) • Cloud based architecture • Standardized or flexible data models • What should the data persistence layer be for OSEHRA? DoD/VA iEHR? • Different or same application and analytic data stores?
OSEHRA AWG SQL vs NOSQL Discussion July 3, 2012
Illustrative References • CIO guide to NOSQL • Data rEvolution • NOSQL data stores • RDBMS to NOSQL • MongoDB • Cassandra vs. MongoDB vs. CouchDB vs. etc.
Download Full Practical Smart Device Design and Construction: Understanding Smart Technologies and How to Build Them Yourself Christopher Harrold PDF All Chapters