Scribd
Upload
8 views2 pages

Day 06

Uploaded by

raviduramesh11
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views2 pages

Day 06

Uploaded by

raviduramesh11
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Aspect SQL DBMS NoSQL DBMS

Structure and • Data Model: Relational model, • Data Model: Non-relational, with
Data Model where data is organized into data stored in various formats like
tables with rows and columns. documents, key-value pairs,
• Schema: Fixed schema, requiring columns, or graphs.
predefined structures and • Schema: Schema-less or flexible
relationships. schema, allowing for changes in data
• Suitability: Best for structured structure without redesigning the
data with clear relationships and entire database.
dependencies. • Suitability: Ideal for semi-structured
• Examples: MySQL, PostgreSQL, or unstructured data, which can be
Oracle, SQL Server. dynamic and vary over time.
• Examples: MongoDB, Cassandra,
Redis, Neo4j.

Scalability • Vertical Scalability: Typically • Horizontal Scalability: Designed to


scales vertically by increasing the scale horizontally by adding more
resources (CPU, memory) of a servers to a distributed network.
single server. • Advantages: Better suited for
• Challenges: Vertical scaling has applications requiring scalability
limitations and can be costly, as across multiple servers, like cloud-
adding resources to a single based applications handling large
server may have diminishing volumes of data.
returns.

ACID vs. BASE • ACID Compliance: Ensures • BASE Compliance: Stands for
Properties Atomicity, Consistency, Basically Available, Soft state,
Isolation, and Durability, Eventual consistency. It sacrifices
making it reliable for some level of immediate
applications where data consistency for availability and
consistency is critical (e.g., speed.
banking systems). • Use Case: Suitable for applications
• Use Case: Preferred for where real-time performance is
transactions requiring high prioritized over strict consistency,
data integrity. such as social media or streaming
platforms.

Query Language • Language: Uses SQL • Language: Varies depending on


(Structured Query Language) the database type. For instance:
for querying data.
• Standardization: SQL is o Document databases (like
standardized, so users can MongoDB) use JSON-based
queries.
generally switch between o Graph databases (like Neo4j)
SQL-based systems with use languages such as Cypher.
minimal changes.
• Flexibility: Allows different query
methods suited to the data model
but lacks a standardized query
language across all NoSQL
databases.

Flexibility and • Flexibility: Less flexible • Flexibility: Highly flexible with


Use Cases because of the fixed schema schema-less structures, making it
and structured data easy to add or change data fields.
requirements. • Common Use Cases: Big data
• Common Use Cases: applications, IoT data, real-time
Traditional business analytics, social networks, and
applications like accounting content management systems.
systems, enterprise
applications, and applications
requiring multi-step
transactions.

Performance • Performance: Typically • Performance: Optimized for high-


performs better with complex speed performance with large
querying on structured data, data sets, especially in distributed
thanks to powerful SQL environments.
operations and indexing. • Advantages: Fast for operations
• Limitations: Not optimized that require quick reads and
for large-scale, distributed, or writes, especially for unstructured
real-time data processing. or semi-structured data.

Data Integrity • Data Integrity: Ensures high • Data Integrity: Less focused on
and Consistency data integrity due to ACID data integrity and may relax
properties and strong consistency for better availability
relational constraints (foreign and partition tolerance (as per the
keys, primary keys, etc.). CAP theorem).
• Consistency: Consistent reads • Consistency: Uses eventual
and writes; all transactions consistency in distributed
follow ACID principles. systems, meaning data might not
be immediately consistent across
all nodes but will eventually
synchronize.

You might also like