SQL vs. NoSQL. It's always a hard choice.

Apr 28, 2017Download as PPTX, PDF2 likes382 views

This will be an interesting and sometimes fun session with a small demo. This session will answer some of your questions and force you to think about new questions. It will not be very technical, so it's ok for choose another more technical session from the schedule :) But if will decide to come, I can assure you, that you will not be disappointed. We will do a thought experiment with one famous public high-loaded website, will look at advantages and disadvantages of SQL and NoSQL databases, and will choose the best database engine for it.

SQL vs NoSQL
It’s Always a Hard Choice
Denis Reznik
Data Architect at Intapp, Inc.
Microsoft Data Platform MVP

About me
• Denis Reznik
• Kyiv, Ukraine
• Data Architect at Intapp, Inc.
• Microsoft Data Platform MVP
• Co-Founder Ukrainian Data Community
• PASS Regional Mentor, Central, and Eastern Europe
• Author of “SQL Server MVP Deep Dives 2” Chapter 19
2 |

Database History
1960s 1970s 1980s 1990s 2000s Nowadays
Object
Databases
RDMS
Commercial
Success
SQL
RDBMS
Ingress
System R
E.F. Codd’s
Paper
CODASYL
IMS
NoSQL
(Johan Oskarsson)
NewSQL (?)
Google BigTable
Paper
Amazon Dynamo
Paper

Agenda
• Criteria #1
• Criteria #2
• Criteria #3
• Criteria #4
• Criteria #5
• Criteria #6
• Criteria #7

SQL vs. NoSQL. It's always a hard choice.

Databases
Graph
Document
Relational
Column-Family
Key-Value

Domain Model
Questions Answers
Users
Comments Votes

Sample Workload
• 4 million users
• 8 million questions
• 40 million answers
• As a network #54 site for traffic in the world
• 560 million page views a month
• Peak is more like 2600-3000 requests/sec on most
weekdays.
source: https://www.youtube.com/watch?v=t6kM2EM6so4

Scalability
• Scale up
• Very easy to scale
• Always have a limit
• Hardware is expensive
• Scale-out
• Relatively tricky scaling
• Theoretically infinite scale
• Can be done on commodity hardware

Durability
ACID
• D – for Durability
• Not all NoSQL databases are
durable (at least by default)

Cost
• Hardware
• Big servers are expensive
• Small servers are cheep
• Small servers can be easily replaced
• License
• A lot of NoSQL databases are free
• There are free RDBMS as well
• Scale Out is more useful for free software
• Support
• MSSQL forgives you more than MySQL

Real Architecture of StackOverflow
source: https://www.youtube.com/watch?v=t6kM2EM6so4

Summary
• Tools
• Domain
• Workload
• Scalability
• Durability
• Cost
• Knowledge
• Polyglot Persistence

More Points
• “Respect the problem” (c)
• Think about the future workload grows
• Think about the future application changes
• Database itself, even if it is blazing fast, is not a purpose of
not to use cache
• Consider cloud database offers
• Consider Polyglot Persistence
• Consider using service tier for data access in application
• Easier database exchange
• Tire scaling
• A/B testing

Thank you!
Denis Reznik
Twitter: @denisreznik
Email: denisreznik@gmail.com
Blog: http://reznik.uneta.com.ua
Facebook: https://www.facebook.com/denis.reznik.5
LinkedIn: http://ua.linkedin.com/pub/denis-reznik/3/502/234

Если раньше при старте нового проекта нам нужно было выбрать одну из доступных на тот момент SQL баз данных, то за последние 5 лет ситуация кардинально изменилась. Теперь выбор стал гораздо сложнее. SQL или NoSQL? Сloud или on-premises? Если SQL/NoSQL - то какая именно? А может использовать и то и другое? В данном докладе мы постараемся представить общий обзор доступных сегодня решений для хранения данных и определиться с критериями выбора.

Rdbms vs. no sqlAmar Jagdale

NOSQL vs SQLMohammed Fazuluddin

The document compares NoSQL and SQL databases. It notes that NoSQL databases are non-relational and have dynamic schemas that can accommodate unstructured data, while SQL databases are relational and have strict, predefined schemas. NoSQL databases offer more flexibility in data structure, but SQL databases provide better support for transactions and data integrity. The document also discusses differences in queries, scaling, and consistency between the two database types.

Selecting best NoSQL Mohammed Fazuluddin

The document discusses factors to consider when selecting a NoSQL database management system (DBMS). It provides an overview of different NoSQL database types, including document databases, key-value databases, column databases, and graph databases. For each type, popular open-source options are described, such as MongoDB for document databases, Redis for key-value, Cassandra for columnar, and Neo4j for graph databases. The document emphasizes choosing a NoSQL solution based on application needs and recommends commercial support for production systems.

Sql vs NO-SQL database differences explainedSatya Pal

This document compares SQL and NoSQL databases. It outlines key differences between the two types of databases such as their data structures (tables vs documents/key-value pairs), schemas (strict vs dynamic), scalability (vertical vs horizontal), and query languages (SQL vs unstructured). Examples of popular SQL databases discussed are MySQL, MS-SQL Server, and Oracle. Examples of NoSQL databases discussed are MongoDB, CouchDB, and Redis. The document provides an overview of each example database's features and benefits.

Sql vs NoSQLRTigger

The document provides an overview of SQL vs NoSQL databases. It discusses how RDBMS systems focus on ACID properties to ensure consistency but sacrifice availability and scalability. NoSQL systems embrace the CAP theorem, prioritizing availability and partition tolerance over consistency to better support distributed and cloud-scale architectures. The document outlines different NoSQL database models and how they are suited for high volume operations through an asynchronous and eventually consistent approach.

NoSql Data Managementsameerfaizan

NoSQL, as many of you may already know, is basically a database used to manage huge sets of unstructured data, where in the data is not stored in tabular relations like relational databases. Most of the currently existing Relational Databases have failed in solving some of the complex modern problems like: • Continuously changing nature of data - structured, semi-structured, unstructured and polymorphic data. • Applications now serve millions of users in different geo-locations, in different timezones and have to be up and running all the time, with data integrity maintained • Applications are becoming more distributed with many moving towards cloud computing. NoSQL plays a vital role in an enterprise application which needs to access and analyze a massive set of data that is being made available on multiple virtual servers (remote based) in the cloud infrastructure and mainly when the data set is not structured. Hence, the NoSQL database is designed to overcome the Performance, Scalability, Data Modelling and Distribution limitations that are seen in the Relational Databases.

SQL vs NoSQLJacinto Limjap

This document discusses SQL versus NoSQL databases. NoSQL databases are better suited for internet-scale applications with massive amounts of data and users due to their ability to provide high availability, high performance, and horizontal scalability. NoSQL databases sacrifice strict ACID properties for looser eventual consistency in order to better serve highly distributed systems. SQL remains preferable when strict ACID properties are required. The document provides examples of MongoDB and concludes that the right database choice depends on the specific needs and use case.

What is NoSQL and CAP TheoremRahul Jain

This document discusses NoSQL and the CAP theorem. It begins with an introduction of the presenter and an overview of topics to be covered: What is NoSQL and the CAP theorem. It then defines NoSQL, provides examples of major NoSQL categories (document, graph, key-value, and wide-column stores), and explains why NoSQL is used, including to handle large, dynamic, and distributed data. The document also explains the CAP theorem, which states that a distributed data store can only satisfy two of three properties: consistency, availability, and partition tolerance. It provides examples of how to choose availability over consistency or vice versa. Finally, it concludes that both SQL and NoSQL have valid use cases and a combination

Sql vs nosqlNick Verschueren

The document compares SQL and NoSQL databases, discussing their characteristics and use cases. It provides details on SQL databases, the scalability arguments for NoSQL, and tradeoffs of SQL features like ACID compliance in NoSQL systems. It also outlines several major types of NoSQL databases like key-value, column-oriented, document, and graph stores, comparing their data models, performance, scalability, and functionality. The document advises considering factors like the problem, costs, programming needs, and performance requirements when choosing a database type.

NoSQL DatabasesBADR

This document provides an overview of different database types including relational, NoSQL, document, key-value, graph, and column family databases. It discusses the history and drivers behind the development of NoSQL databases, as well as concepts like horizontal scaling, the CAP theorem, and eventual consistency. Specific databases are also summarized, including MongoDB, Redis, Neo4j, and HBase.

No SQL- The Future Of Data StorageBethmi Gunasekara

NoSQL vs SQL (by Dmitriy Beseda, JS developer and coach Binary Studio Academy)Binary Studio

NoSQL Architecture OverviewChristopher Foot

The presentation begins with an overview of the growth of non-structured data and the benefits NoSQL products provide. It then provides an evaluation of the more popular NoSQL products on the market including MongoDB, Cassandra, Neo4J, and Redis. With NoSQL architectures becoming an increasingly appealing database management option for many organizations, this presentation will help you effectively evaluate the most popular NoSQL offerings and determine which one best meets your business needs.

Nonrelational DatabasesUdi Bauman

Non-relational databases were developed to address the problems that traditional relational databases have in handling web-scale applications with massive amounts of data and users. They sacrifice consistency to gain availability and partition tolerance. Examples include BigTable, HBase, Dynamo, and Cassandra. They provide benefits like massive scalability, high availability, and elasticity through techniques like consistent hashing, replication, and MapReduce processing.

SQL vs NoSQLSkills Matter

This document compares SQL and NoSQL databases. It discusses the history of SQL databases and how NoSQL databases were developed to address modern demands like scaling, fault tolerance, and conflicting queries arriving at different nodes. The document notes that NoSQL databases generally offer more flexible data models and eventual consistency, but at the cost of less predictable behavior compared to SQL databases.

NoSQL Slideshare Presentation Ericsson Labs

This document provides an overview of NoSQL databases and HBase. It discusses why NoSQL databases are gaining popularity due to trends in data and architecture. It also summarizes the CAP theorem and how different databases balance consistency, availability and partition tolerance. The document describes research activities including evaluating HBase for telco usage and performing bulk processing tests on HBase. It finds that while HBase can scale horizontally, managing compaction storms and small files is challenging.

SQL & NoSQLAhmad Awsaf-uz-zaman

This document provides an overview of SQL and NoSQL databases. It defines SQL as a language used to communicate with relational databases, allowing users to query, manipulate, and retrieve data. NoSQL databases are defined as non-relational and allow for flexible schemas. The document compares key aspects of SQL and NoSQL such as data structure, querying, scalability and provides examples of popular SQL and NoSQL database systems. It concludes that both SQL and NoSQL databases will continue to be important with polyglot persistence, using the best database for each storage need.

Introduction to NoSQLDimitar Danailov

Introduction to NoSQLPolarSeven Pty Ltd

The document summarizes a meetup about NoSQL databases hosted by AWS in Sydney in 2012. It includes an agenda with presentations on Introduction to NoSQL and using EMR and DynamoDB. NoSQL is introduced as a class of databases that don't use SQL as the primary query language and are focused on scalability, availability and handling large volumes of data in real-time. Common NoSQL databases mentioned include DynamoDB, BigTable and document databases.

NoSQL Data ArchitecturePatternsMaynooth University

This document provides an overview of NoSQL data architecture patterns, including key-value stores, graph stores, and column family stores. It describes key aspects of each pattern such as how keys and values are structured. Key-value stores use a simple key-value approach with no query language, while graph stores are optimized for relationships between objects. Column family stores use row and column identifiers as keys and scale well for large volumes of data.

Data Modeling for NoSQLTony Tam

- Data modeling for NoSQL databases is different than relational databases and requires designing the data model around access patterns rather than object structure. Key differences include not having joins so data needs to be duplicated and modeling the data in a way that works for querying, indexing, and retrieval speed. - The data model should focus on making the most of features like atomic updates, inner indexes, and unique identifiers. It's also important to consider how data will be added, modified, and retrieved factoring in object complexity, marshalling/unmarshalling costs, and index maintenance. - The _id field can be tailored to the access patterns, such as using dates for time-series data to keep recent

Non relational databases-no sqlRam kumar

This document provides an overview of non-relational (NoSQL) databases. It discusses the history and characteristics of NoSQL databases, including that they do not require rigid schemas and can automatically scale across servers. The document also categorizes major types of NoSQL databases, describes some popular NoSQL databases like Dynamo and Cassandra, and discusses benefits and limitations of both SQL and NoSQL databases.

NOSQL Databases types and UsesSuvradeep Rudra

SQL vs NoSQL, an experiment with MongoDBMarco Segato

Big Challenges in Data Modeling: NoSQL and Data ModelingDATAVERSITY

Big Data and NoSQL have led to big changes In the data environment, but are they all in the best interest of data? Are they technologies that "free us from the harsh limitations of relational databases?" In this month's webinar, we will be answering questions like these, plus: Have we managed to free organizations from having to do Data Modeling? Is there a need for a Data Modeler on NoSQL projects? If we build Data Models, which types will work? If we build Data Models, how will they be used? If we build Data Models, when will they be used? Who will use Data Models? Where does Data Quality happen? Finally, we will wrap with 10 tips for data modelers in organizations incorporating NoSQL in their modern Data Architectures.

Relational vs. Non-RelationalPostgreSQL Experts, Inc.

This document compares relational and non-relational databases. It discusses how in 2003 the main databases were relational, but by 2010 non-relational databases grew popular in the "NoSQL movement". However, the document argues that there are no truly new database designs and that relational and non-relational databases can be combined. It advises to choose a database based on the specific problem and features needed rather than general classifications. The document provides examples of which types of databases fit certain data and access needs.

NoSQLDatabasesAdi Challa

The document discusses the history and concepts of NoSQL databases. It notes that traditional single-processor relational database management systems (RDBMS) struggled to handle the increasing volume, velocity, variability, and agility of data due to various limitations. This led engineers to explore scaled-out solutions using multiple processors and NoSQL databases, which embrace concepts like horizontal scaling, schema flexibility, and high performance on commodity hardware. Popular NoSQL database models include key-value stores, column-oriented databases, document stores, and graph databases.

Einführung in RavenDBNETUserGroupBern

Bei all dem Hype rund um NoSQL übersieht man gerne wie viele einsatzbereite Produkte darauf warten unser Entwicklerleben zu vereinfachen. Eines dieser Produkte ist RavenDB, eine dokumentenorientierte Datenbank mit Transaktionsunterstützung. Im Gegensatz zu vielen NoSQL-Lösungen ist RavenDB voll in die .Net-Welt integriert. So kann man seine Abfragen mittels LINQ formulieren und muss nicht auf JavaScript setzen. Die grosse Erfahrung von Oren Eini bei der Optimierung von NHibernate und Entity Framework wurden in RavenDB aufgenommen. So hilft eine frühzeitige Erkennung von Select N+1 Abfragen spätere Probleme in der Produktion zu verhindern. Neben diesen Eigenheiten wird uns Johnny Graber auch zeigen was es alles für Einsatzmöglichkeiten gibt. Die Flexibilität von NoSQL gepaart mit der Einfachheit von RavenDB ist dabei keineswegs nur etwas für grosse Firmen wie Google, Facebook oder Twitter - der nächste Prototyp kann davon genauso gut profitieren.

More Related Content

What's hot (20)

SQL vs NoSQLJacinto Limjap

What is NoSQL and CAP TheoremRahul Jain

Sql vs nosqlNick Verschueren

NoSQL DatabasesBADR

No SQL- The Future Of Data StorageBethmi Gunasekara

NoSQL vs SQL (by Dmitriy Beseda, JS developer and coach Binary Studio Academy)Binary Studio

NoSQL Architecture OverviewChristopher Foot

Nonrelational DatabasesUdi Bauman

SQL vs NoSQLSkills Matter

NoSQL Slideshare Presentation Ericsson Labs

SQL & NoSQLAhmad Awsaf-uz-zaman

Introduction to NoSQLDimitar Danailov

Introduction to NoSQLPolarSeven Pty Ltd

NoSQL Data ArchitecturePatternsMaynooth University

Data Modeling for NoSQLTony Tam

Non relational databases-no sqlRam kumar

NOSQL Databases types and UsesSuvradeep Rudra

SQL vs NoSQL, an experiment with MongoDBMarco Segato

Big Challenges in Data Modeling: NoSQL and Data ModelingDATAVERSITY

Relational vs. Non-RelationalPostgreSQL Experts, Inc.

SQL vs NoSQLJacinto Limjap

What is NoSQL and CAP TheoremRahul Jain

Sql vs nosqlNick Verschueren

NoSQL DatabasesBADR

No SQL- The Future Of Data StorageBethmi Gunasekara

NoSQL vs SQL (by Dmitriy Beseda, JS developer and coach Binary Studio Academy)Binary Studio

NoSQL Architecture OverviewChristopher Foot

Nonrelational DatabasesUdi Bauman

SQL vs NoSQLSkills Matter

NoSQL Slideshare Presentation Ericsson Labs

SQL & NoSQLAhmad Awsaf-uz-zaman

Introduction to NoSQLDimitar Danailov

Introduction to NoSQLPolarSeven Pty Ltd

NoSQL Data ArchitecturePatternsMaynooth University

Data Modeling for NoSQLTony Tam

Non relational databases-no sqlRam kumar

NOSQL Databases types and UsesSuvradeep Rudra

SQL vs NoSQL, an experiment with MongoDBMarco Segato

Big Challenges in Data Modeling: NoSQL and Data ModelingDATAVERSITY

Relational vs. Non-RelationalPostgreSQL Experts, Inc.

Similar to SQL vs. NoSQL. It's always a hard choice. (20)

NoSQLDatabasesAdi Challa

Einführung in RavenDBNETUserGroupBern

My sql competitive updatexKinAnx

The document summarizes competitive advantages of MySQL compared to commercial and open source databases. It highlights that commercial databases have much higher total cost of ownership, are more complex, and have licensing restrictions. Express databases are found to have technical restrictions that prevent scaling. While other open source databases lack commercial backing and support. The document provides recommendations and questions to consider when evaluating MySQL against other database options.

Oracle Week 2016 - Modern Data ArchitectureArthur Gimpel

This document discusses modern operational data architectures and the use of both relational and NoSQL databases. It provides an overview of relational databases and their ACID properties. While relational databases dominate the market, they have limitations around scalability, flexibility, and performance. NoSQL databases offer alternatives like horizontal scaling and flexible schemas. Key-value stores are best for caching, sessions, and serving data, while document stores are popular for hierarchical and search use cases. Graph databases excel at link analysis. The document advocates a polyglot persistence approach using multiple database types according to their strengths. It provides examples of search architectures using both database-centric and application-centric distribution approaches.

Startup Bootcamp - Intro to NoSQL/Big Data by DataZoneIdan Tohami

Arthur Gimpel gave an introduction to Big Data and NoSQL databases. He defined the 3 V's of Big Data as volume, velocity and variety. He explained different NoSQL database types including key-value, graph and document databases. Key-value databases provide fast access but querying values is challenging. Graph databases are useful for relationships between entities. Document databases commonly store JSON and include popular examples like MongoDB. Choosing the right database is important and replacing them is not cheap.

Introduction to NoSQL and MongoDBAhmed Farag

This document provides an introduction to NoSQL and MongoDB. It outlines that NoSQL databases are used to manage unstructured data and overcome limitations of relational databases. MongoDB is introduced as a popular document-oriented NoSQL database that stores data as JSON-like documents. Key features of MongoDB include high performance, scalability, rich query language, and automatic replication for high availability.

Transform your DBMS to drive engagement innovation with Big DataAshnikbiz

This document discusses how organizations can save money on database management systems (DBMS) by moving from expensive commercial DBMS to more affordable open-source options like PostgreSQL. It notes that PostgreSQL has matured and can now handle mission critical workloads. The document recommends partnering with EnterpriseDB to take advantage of their commercial support and features for PostgreSQL. It highlights how customers have seen cost savings of 35-80% by switching to PostgreSQL and been able to reallocate funds to new business initiatives.

Greatdebate Postgres vs MysqlKrishna Infosoft

This document summarizes a presentation comparing PostgreSQL and MySQL databases. It outlines the strengths and weaknesses of each, including PostgreSQL's strong advanced features and security capabilities versus its lack of integrated replication. MySQL's strengths are its integrated replication and performance, while its weaknesses include immature security and an "closed" open source community. A variety of application types are described as better fits for each database. The document concludes with information about EnterpriseDB, a company that provides commercial support for PostgreSQL.

20-NoSQLMongoDbiig data analytics hB.pdfssuser2d043c

Baisc introduction of mongodb for beginnpoojamehta654564

An Enterprise Architect's View of MongoDBMongoDB

This document discusses how MongoDB can help enterprises meet modern data and application requirements. It outlines the many new technologies and demands placing pressure on enterprises, including big data, mobile, cloud computing, and more. Traditional databases struggle to meet these new demands due to limitations like rigid schemas and difficulty scaling. MongoDB provides capabilities like dynamic schemas, high performance at scale through horizontal scaling, and low total cost of ownership. The document examines how MongoDB has been successfully used by enterprises for use cases like operational data stores and as an enterprise data service to break down silos.

Add Redis to Postgres to Make Your Microservices Go Boom!Dave Nielsen

Webinar: The Future of SQLCrate.io

NoSQL databases like MongoDB, Elasticsearch, and Cassandra are synonymous with scalability, search, and developer agility. But there’s a downside...having to give up the ease and comfort of SQL. Or do you? Join this webcast to learn how the newest databases, like CrateDB and CockroachDB deliver the benefits of NoSQL with the ease of SQL by building SQL engines on top of custom NoSQL technology stacks. Database industry veteran Andy Ellicott, who helped launch Vertica, VoltDB, Cloudant, and now with Crate.io, will provide a no-BS view of current DBMS architectures and predictions for the future of data. If you’re a DBMS user, this webcast will help you make sense of a very crowded DBMS market and make better-informed decisions for your new tech stacks.

Making MySQL Flexible with ParElastic Database Scalability, Amrith Kumar, Fou...✔ Eric David Benari, PMP

The document discusses scalability issues with databases and proposes solutions. It introduces the concept of parallel databases which improve performance through linear scaling of reads, writes, joins and other operations. ParElastic is introduced as a parallel database architecture built on MySQL that addresses scalability through database virtualization and horizontal scaling in a way that is elastic and transparent to applications.

NoSQLRadu Vunvulea

The document discusses NoSQL databases and their advantages compared to SQL databases. It defines NoSQL as any database that is not relational and describes the main categories of NoSQL databases - key-value stores, document databases, wide column stores like BigTable, and graph databases. It also covers common use cases for different NoSQL databases and examples of companies using NoSQL technologies like MongoDB, Cassandra, and HBase.

A peek into the futurePrateek Chauhan

This document discusses trends in database technologies and big data. It begins by questioning whether relational databases are always the most efficient way to store data and whether companies like Facebook use traditional databases. It then covers object-relational mapping (ORM), which provides a bridge between object-oriented programming languages and relational databases. The document also discusses NoSQL databases as an alternative for handling large, unstructured "big data" and provides examples like document stores, key-value stores, and graph databases. It concludes by defining big data and discussing the types, analysis, and market size of big data technologies.

Building FoundationDBFoundationDB

FoundationDB is a next-generation database that aims to provide high performance transactions at massive scale through a distributed design. It addresses limitations of NoSQL databases by providing a transactional, fault-tolerant foundation using tools like the Flow programming language. FoundationDB has demonstrated high performance that exceeds other NoSQL databases, and provides ease of scaling, building abstractions, and operation through its transactional design and automated partitioning. The goal is to solve challenges of state management so developers can focus on building applications.

The Great Debate: PostgreSQL vs MySQLEDB

This document summarizes a presentation comparing PostgreSQL and MySQL databases. It outlines the strengths and weaknesses of each, including PostgreSQL's strong advanced features and flexible licensing but lack of integrated replication, and MySQL's replication capabilities but immature security and programming models. It also discusses common application types for each database and provides an overview of the EnterpriseDB company.

When to Use MongoDB...and When You Should Not...MongoDB

MongoDB is well-suited for applications that require: - A flexible data model to handle diverse and changing data sets - Strong performance on mixed workloads involving reads, writes, and updates - Horizontal scalability to grow with increasing user needs and data volume Some common use cases that leverage MongoDB's strengths include mobile apps, real-time analytics, content management, and IoT applications involving sensor data. However, MongoDB is less suited for tasks requiring full collection scans under load, high write availability, or joins across collections.

ECMDay2015 - Kent Agerlund – Configuration Manager 2012 – A Site ReviewKenny Buntinx

Ever experienced sluggish ConfigMgr administrator console performance or collections taking forever to refresh? Join Kent Agerlund as he will walk you thru a ConfigMgr site review and reveal why so many ConfigMgr installations don’t perform as they should. This sessions will be packed with tip and tricks, SQL secrets and PowerShell scripts that will optimize your environment and bring ConfigMgr into the state it was supposed to be from the beginning

NoSQLDatabasesAdi Challa

Einführung in RavenDBNETUserGroupBern

My sql competitive updatexKinAnx

Oracle Week 2016 - Modern Data ArchitectureArthur Gimpel

Startup Bootcamp - Intro to NoSQL/Big Data by DataZoneIdan Tohami

Introduction to NoSQL and MongoDBAhmed Farag

Transform your DBMS to drive engagement innovation with Big DataAshnikbiz

Greatdebate Postgres vs MysqlKrishna Infosoft

20-NoSQLMongoDbiig data analytics hB.pdfssuser2d043c

Baisc introduction of mongodb for beginnpoojamehta654564

An Enterprise Architect's View of MongoDBMongoDB

Add Redis to Postgres to Make Your Microservices Go Boom!Dave Nielsen

Webinar: The Future of SQLCrate.io

Making MySQL Flexible with ParElastic Database Scalability, Amrith Kumar, Fou...✔ Eric David Benari, PMP

NoSQLRadu Vunvulea

A peek into the futurePrateek Chauhan

Building FoundationDBFoundationDB

The Great Debate: PostgreSQL vs MySQLEDB

When to Use MongoDB...and When You Should Not...MongoDB

ECMDay2015 - Kent Agerlund – Configuration Manager 2012 – A Site ReviewKenny Buntinx

Recently uploaded (20)

EDU533 DEMO.pptxccccvbnjjkoo jhgggggbbbbJessaMaeEvangelista2

Template_A3nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnncegiver630

Telangana State, India’s newest state that was carved from the erstwhile state of Andhra Pradesh in 2014 has launched the Water Grid Scheme named as ‘Mission Bhagiratha (MB)’ to seek a permanent and sustainable solution to the drinking water problem in the state. MB is designed to provide potable drinking water to every household in their premises through piped water supply (PWS) by 2018. The vision of the project is to ensure safe and sustainable piped drinking water supply from surface water sources

Thingyan is now a global treasure! See how people around the world are search...Pixellion

chapter 4 Variability statistical research .pptxjustinebandajbn

IAS-slides2-ia-aaaaaaaaaaain-business.pdfmcgardenlevi9

1. Briefing Session_SEED with Hon. Governor Assam - 27.10.pdfSimran112433

Flip flop presenation-Presented By Mubahir khan.pptxmubashirkhan45461

Data Science Courses in India iim skillsdharnathakur29

This comprehensive Data Science course is designed to equip learners with the essential skills and knowledge required to analyze, interpret, and visualize complex data. Covering both theoretical concepts and practical applications, the course introduces tools and techniques used in the data science field, such as Python programming, data wrangling, statistical analysis, machine learning, and data visualization.

Data Analytics Overview and its applicationsJanmejayaMishra7

Ch3MCT24.pptx measure of central tendencyayeleasefa2

Ppt. Nikhil.pptxnshwuudgcudisisshvehsjkspanchariyasahil

Secure_File_Storage_Hybrid_Cryptography.pptx..yuvarajreddy2002

VKS-Python Basics for Beginners and advance.pptxVinod Srivastava

Just-In-Timeasdfffffffghhhhhhhhhhj Systems.pptssuser5f8f49

Perencanaan Pengendalian-Proyek-Konstruksi-MS-PROJECT.pptxPareaRusan

Day 1 - Lab 1 Reconnaissance Scanning with NMAP, Vulnerability Assessment wit...Abodahab

Adobe Analytics NOAM Central User Group April 2025 Agent AI: Uncovering the S...gmuir1066

Molecular methods diagnostic and monitoring of infection - Repaired.pptx7tzn7x5kky

md-presentHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHation.pptxfatimalazaar2004

C++_OOPs_DSA1_Presentation_Template.pptxaquibnoor22079

EDU533 DEMO.pptxccccvbnjjkoo jhgggggbbbbJessaMaeEvangelista2

Template_A3nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnncegiver630

Thingyan is now a global treasure! See how people around the world are search...Pixellion

chapter 4 Variability statistical research .pptxjustinebandajbn

IAS-slides2-ia-aaaaaaaaaaain-business.pdfmcgardenlevi9

1. Briefing Session_SEED with Hon. Governor Assam - 27.10.pdfSimran112433

Flip flop presenation-Presented By Mubahir khan.pptxmubashirkhan45461

Data Science Courses in India iim skillsdharnathakur29

Data Analytics Overview and its applicationsJanmejayaMishra7

Ch3MCT24.pptx measure of central tendencyayeleasefa2

Ppt. Nikhil.pptxnshwuudgcudisisshvehsjkspanchariyasahil

Secure_File_Storage_Hybrid_Cryptography.pptx..yuvarajreddy2002

VKS-Python Basics for Beginners and advance.pptxVinod Srivastava

Just-In-Timeasdfffffffghhhhhhhhhhj Systems.pptssuser5f8f49

Perencanaan Pengendalian-Proyek-Konstruksi-MS-PROJECT.pptxPareaRusan

Day 1 - Lab 1 Reconnaissance Scanning with NMAP, Vulnerability Assessment wit...Abodahab

Adobe Analytics NOAM Central User Group April 2025 Agent AI: Uncovering the S...gmuir1066

Molecular methods diagnostic and monitoring of infection - Repaired.pptx7tzn7x5kky

md-presentHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHation.pptxfatimalazaar2004

C++_OOPs_DSA1_Presentation_Template.pptxaquibnoor22079

SQL vs. NoSQL. It's always a hard choice.

1. SQL vs NoSQL It’s Always a Hard Choice Denis Reznik Data Architect at Intapp, Inc. Microsoft Data Platform MVP

2. About me • Denis Reznik • Kyiv, Ukraine • Data Architect at Intapp, Inc. • Microsoft Data Platform MVP • Co-Founder Ukrainian Data Community • PASS Regional Mentor, Central, and Eastern Europe • Author of “SQL Server MVP Deep Dives 2” Chapter 19 2 |

3. Database History 1960s 1970s 1980s 1990s 2000s Nowadays Object Databases RDMS Commercial Success SQL RDBMS Ingress System R E.F. Codd’s Paper CODASYL IMS NoSQL (Johan Oskarsson) NewSQL (?) Google BigTable Paper Amazon Dynamo Paper

4. NoSQL SQL

5. Agenda • Criteria #1 • Criteria #2 • Criteria #3 • Criteria #4 • Criteria #5 • Criteria #6 • Criteria #7

6. Tools Criteria #1

8. Databases Graph Document Relational Column-Family Key-Value

9. Domain Criteria #2

10. Q&A Web Site (StackOverflow)

11. Domain Model Questions Answers Users Comments Votes

12. Workload Criteria #3

13. Sample Workload • 4 million users • 8 million questions • 40 million answers • As a network #54 site for traffic in the world • 560 million page views a month • Peak is more like 2600-3000 requests/sec on most weekdays. source: https://www.youtube.com/watch?v=t6kM2EM6so4

14. Scalability Criteria #4

15. Scalability • Scale up • Very easy to scale • Always have a limit • Hardware is expensive • Scale-out • Relatively tricky scaling • Theoretically infinite scale • Can be done on commodity hardware

16. Durability Criteria #5

17. Durability ACID • D – for Durability • Not all NoSQL databases are durable (at least by default)

18. Cost Criteria #6

19. Cost • Hardware • Big servers are expensive • Small servers are cheep • Small servers can be easily replaced • License • A lot of NoSQL databases are free • There are free RDBMS as well • Scale Out is more useful for free software • Support • MSSQL forgives you more than MySQL

20. Knowledge Criteria #7

22. Polyglot Persistence Criteria #8

23. Real Architecture of StackOverflow source: https://www.youtube.com/watch?v=t6kM2EM6so4

24. Summary • Tools • Domain • Workload • Scalability • Durability • Cost • Knowledge • Polyglot Persistence

25. More Points • “Respect the problem” (c) • Think about the future workload grows • Think about the future application changes • Database itself, even if it is blazing fast, is not a purpose of not to use cache • Consider cloud database offers • Consider Polyglot Persistence • Consider using service tier for data access in application • Easier database exchange • Tire scaling • A/B testing

26. Thank you! Denis Reznik Twitter: @denisreznik Email: [email protected] Blog: http://reznik.uneta.com.ua Facebook: https://www.facebook.com/denis.reznik.5 LinkedIn: http://ua.linkedin.com/pub/denis-reznik/3/502/234

SQL vs. NoSQL. It's always a hard choice.

Recommended

More Related Content

What's hot (20)

Similar to SQL vs. NoSQL. It's always a hard choice. (20)

Recently uploaded (20)

SQL vs. NoSQL. It's always a hard choice.