a.

Fundamental Differences Between Traditional SQL and NoSQL Databases and Their Impact
Traditional SQL (Relational) databases organize data in a structured format using tables
(relations). NoSQL (Not Only SQL) databases emerged as a response to the limitations of
relational models, offering a non-relational approach.
Feature Traditional SQL (Relational Data Model) NoSQL Databases
Non-relational approach; tailored
Structured format using tables (relations),
Data data modeling. Includes types like
storing data in rows (records) and columns
Structure document, key-value, wide-column,
(attributes).
and graph stores.
Flexibility: Freedom from rigid
Schema Rigidity: Once defined, modifying
Schema schemas allows data modeling to
the schema can be difficult or time-consuming.
align closely with application needs.
Well-suited for structured data with well- Designed for handling diverse data
Data defined relationships. Can become complex types and massive datasets,
Handling when dealing with large volumes of including semi-structured data (e.g.,
unstructured or semi-structured data. document stores).
Impact on Scalability and Flexibility in Modern Applications
1. Scalability:
◦ SQL Impact: Scaling a relational database to handle massive datasets can be expensive and
cumbersome. Performance may degrade significantly as the data volume grows.
◦ NoSQL Impact: NoSQL databases often boast horizontal scalability, meaning you can
easily add more servers to handle growing data volumes. This ability to effortlessly scale by
adding more servers addresses the scalability limitations of relational systems.
2. Flexibility:
◦ SQL Impact: The schema rigidity in relational databases is a drawback when data
requirements change frequently.
◦ NoSQL Impact: NoSQL provides a more flexible canvas for data modeling, allowing
developers to tailor the database to specific data characteristics and application requirements.
This freedom from rigid schemas enhances flexibility.
b. Primary Characteristics of NoSQL Databases and How They Address Relational Limitations
NoSQL databases are defined by characteristics that directly counteract the structural and scaling
limitations of traditional relational systems.
Primary Characteristics of NoSQL Databases:
1. Non-Relational Approach: NoSQL systems offer a non-relational approach to data storage.
2. Flexible Data Modeling: They provide greater flexibility for data modeling, offering
freedom from the rigid schemas inherent in relational models.
3. Horizontal Scalability: NoSQL databases excel in horizontal scalability, allowing users to
effortlessly scale the database by adding more servers as data grows.
4. Diverse Flavors: NoSQL databases come in various types, each optimized for different data
structures, including document stores, key-value stores, wide-column stores, and graph
databases.
5. Performance Optimization: They are often optimized for specific query patterns, enabling
faster performance for certain workloads compared to relational databases.
6. Cost-Effectiveness: For very large datasets, NoSQL databases can potentially be more cost-
effective to manage.
Addressing Relational Limitations in Handling Large-Scale, Unstructured Data:
Traditional relational databases face challenges when dealing with large volumes of unstructured
or semi-structured data, and they struggle with scalability limitations. NoSQL characteristics
directly address these issues:
1. Handling Unstructured/Semi-structured Data: While relational databases are well-suited
for structured data, they are often challenging for efficiently representing unstructured or semi-
structured data. NoSQL addresses this by supporting diverse data types and massive datasets,
with specific types like document stores being ideal for semi-structured data (JSON-like
documents).
2. Large-Scale Data Management: Relational scaling can be expensive and cumbersome.
NoSQL's characteristic of horizontal scalability allows growing data volumes to be handled
seamlessly by adding more servers.
3. Schema Requirements: The freedom from rigid schemas in NoSQL systems addresses the
limitation of schema rigidity in relational databases, which can be a drawback when data
requirements change frequently.
c. Factors Contributing to the Rise of NoSQL Databases
The rise of NoSQL databases was driven primarily by technological evolution and business
needs that highlighted the limitations of the traditional relational data model.
1. Technological Needs Driving Adoption:
• Handling Complex and Diverse Data: Traditional relational databases become complex when
managing large volumes of unstructured or semi-structured data, such as sensor data or social
media posts. NoSQL provided solutions specifically designed to handle these diverse data
types.
• Overcoming Scalability Bottlenecks: Relational databases face limitations where scaling to
handle massive datasets is expensive and cumbersome, often leading to performance
degradation. NoSQL offered horizontal scalability, enabling organizations to seamlessly add
servers to handle growth.
• Addressing Schema Rigidity: In modern, fast-paced applications where data requirements
change often, the schema rigidity of SQL databases—where modifying the schema can be
difficult or time-consuming—became a significant drawback. NoSQL offers greater flexibility
and freedom from rigid schemas.
• Specialized Data Structures: Relational databases are not the best choice for storing and
managing certain data types, such as hierarchical data, multimedia content, or highly
interconnected datasets like social networks. NoSQL addressed this by offering different
"flavors" (e.g., Graph databases for relationships, Document stores for flexibility).
2. Business Needs Driving Adoption:
• Improved Performance: Businesses needing rapid access to data for specific operations found
that NoSQL databases, which are optimized for specific query patterns, could deliver faster
performance than generalized relational databases.
• Cost Efficiency: For organizations managing extremely large datasets, NoSQL solutions
offered a potentially more cost-effective way to manage data compared to scaling expensive
relational infrastructure.
• Application Alignment: The need to tailor database architecture to specific application
requirements—rather than fitting the application to a rigid table structure—drove the adoption of
NoSQL due to its flexible canvas for data modeling.
Question No. 3: Key-Value Stores
a. Architecture, Use Cases, Data Retrieval, Strengths, and Weaknesses of Key-Value Stores
Architecture and Data Retrieval:
Key-value stores are one of the specific flavors of NoSQL databases. They are defined by their
structure where data retrieval is based on unique keys.
Use Cases:
Key-value stores are perfect for simple data structures.
Strengths and Weaknesses:
Aspect Description Citation
They offer fast retrieval based on unique keys. They are ideal for simple
Strengths
data structures.
The provided source material does not specify the weaknesses of key-
Weaknesses N/A
value stores.