SQL vs NoSQL : The Ultimate Database Showdown
SQL vs NoSQL : The Ultimate Database Showdown
SQL v/s NoSQL
RDBMS \ SQL NoSQL
Best for low-velocity data Best Handle high-velocity data
Data arrives from one to a few locations Data moves from & to many locations
Support Complex queries and business logic using JOIN Support simple queries do not support JOIN
Single Point of failure No Dependency on single point failure
Handle data in low to moderate volume Handle data in high volume
Centralized deployment Decentralized deployment
Transactions can write only at one location The transaction can be written from multiple locations
Give Read Scalability Give Read Write Scalability
Support Vertical Scaling, add resources to the server when need more power Support Horizontal Scaling, add node when need more power
Support programming languages like TSQL, PSQL Support programming language like CQL, GQL
Stores data in tables Different data storing formats like document, graph, etc.
Each record has fixed properties Flexible properties
Fix Schema Dynamic \ Flexible Schema
For any change in properties, Schema needs to be altered New Property can be added any time
Support In-Memory Comes up with integrated caching
OLTP & OLAP are 2 types of RDBMS 4 Types of NoSQL Databases
Works on ACID Properties Follows CAP(consistency, availability, partition tolerance)
·Atomicity
·Consistency
·Isolation
·Durability
ACID properties, CAP theorem, Caching, Complex queries, Data analysis, Data retrieval, Data storage, Data volume, Historical data, Horizontal scaling, NoSQL databases, OLAP, OLTP, Performance, RDBMS, Real-time data, SQL vs NOSQL, Scalability, Structured data, Transaction processing, Unstructured data, Vertical scaling, acid principles, olap vs oltp, query optimization, real-time analytics, vertical scaling, data, data engineer, data architecture, big data, acid compliance