ScholarQuill logoScholarQuillUniversity Notes
  • Notes
  • Past Papers
  • Blogs
  • Todo
Login
ScholarQuill logoScholarQuillUniversity Notes
Login
NotesPast PapersBlogsTodo
More
SubjectsDiscussionCGPA CalculatorGPA CalculatorStudent PortalCourse Outline
About
About usPrivacy PolicyReportContact
Notes
Past Papers
Blogs
Todo
Analytics
    Current Subject
    🧩
    Advance Database Management Systems
    COMP3146
    Progress0 / 18 topics
    Topics
    1. Introduction to advance data models such as object relational, object oriented2. File organizations concepts3. Transactional processing4. Concurrency control techniques5. Recovery techniques6. Query processing and optimization7. Database Programming (PL/SQL)8. Database Programming (T-SQL)9. Database Programming (similar technology)10. Integrity and security11. Database Administration (Role management)12. Database Administration (managing database access)13. Database Administration (views)14. Physical database design and tuning15. Distributed database systems16. Emerging research trends in database systems17. MONGO DB18. NO SQL (or similar technologies)
    COMP3146›NO SQL (or similar technologies)
    Advance Database Management SystemsTopic 18 of 18

    NO SQL (or similar technologies)

    3 minread
    438words
    Beginnerlevel

    📚 NoSQL Databases and Similar Technologies


    1. What is NoSQL?

    • NoSQL stands for "Not Only SQL" or "Non-relational".
    • It refers to a broad class of database systems that do not use the traditional relational model.
    • Designed to handle large volumes of unstructured or semi-structured data, with flexible schemas, high scalability, and high performance.

    2. Why NoSQL?

    • RDBMS struggles with scaling horizontally for big data and distributed environments.

    • NoSQL databases handle:

      • Huge data volumes (big data).
      • High velocity data (real-time apps).
      • Diverse data formats (JSON, XML, graphs).
    • Support for schema flexibility and distributed architectures.


    3. Types of NoSQL Databases

    Type Description Example Technologies
    Document Stores Store data as documents (JSON, BSON). Flexible schema. MongoDB, CouchDB, Amazon DocumentDB
    Key-Value Stores Simple key-value pairs for fast lookups. Redis, Riak, DynamoDB
    Column-Family Stores Data stored in columns rather than rows; good for analytical queries. Apache Cassandra, HBase
    Graph Databases Data represented as nodes, edges for relationships. Neo4j, Amazon Neptune, JanusGraph
    Time-Series Databases Optimized for time-stamped data. InfluxDB, TimescaleDB

    4. Key Characteristics of NoSQL

    Characteristic Explanation
    Schema Flexibility No fixed schema; can store varied data formats.
    Scalability Designed to scale horizontally across servers.
    High Availability Replication and failover built-in.
    Eventual Consistency Often trade strict consistency for availability and partition tolerance (CAP theorem).
    Distributed Architecture Data is distributed across multiple nodes.

    5. CAP Theorem Recap

    • No distributed system can simultaneously guarantee:

      • Consistency (C)
      • Availability (A)
      • Partition Tolerance (P)
    • NoSQL databases often choose between:

      • CA (Consistency + Availability)
      • AP (Availability + Partition tolerance)
      • CP (Consistency + Partition tolerance)

    6. Examples of NoSQL Technologies

    Technology Type Use Case
    MongoDB Document Store Content management, real-time analytics
    Cassandra Column Store High write throughput, IoT data
    Redis Key-Value Store Caching, session management
    Neo4j Graph Database Social networks, recommendation engines
    InfluxDB Time-Series DB Monitoring, sensor data

    7. When to Use NoSQL?

    • Data is semi-structured or unstructured.
    • You need high throughput and low latency.
    • Applications require horizontal scalability.
    • Schema may evolve rapidly.
    • Complex relationships or graph data is important.

    8. Advantages

    • Flexible data model adapts to changing needs.
    • Can handle big data and real-time workloads efficiently.
    • Simplifies scaling and distributed data management.
    • Usually simpler to develop with for non-relational data.

    9. Limitations

    • Often lack ACID transactions (though improving).
    • Query languages can be less powerful than SQL.
    • Some tools and skills are less mature.
    • Data consistency can be eventual, not immediate.

    10. Summary Table

    Aspect RDBMS NoSQL
    Schema Fixed schema Flexible schema
    Data Model Tables with rows & columns Documents, key-values, graphs
    Transactions Strong ACID support Limited or eventual consistency
    Scaling Vertical scaling Horizontal scaling
    Query Language SQL Varies (e.g., JSON queries, Cypher)

    Previous topic 17
    MONGO DB

    Past Papers

    Open this section to load past papers

    Click on Show Past Papers to see past papers.
    On This Page
      Reading Stats
      Est. reading time3 min
      Word count438
      Code examples0
      DifficultyBeginner