codingstuff.io
ExploreTutorialsProblemsCS Subjects
Get Started
ExploreTutorialsProblemsCS Subjects
Get Started
codingstuff.io

Master the art of building software through interactive tutorials, real-world problems, and guided projects.

Pune, Maharashtra, India

codingstuffmail@gmail.com

Product

  • Explore
  • Tutorials
  • Problems
  • CS Subjects

Company

  • About
  • Contact
  • Privacy Policy
  • Terms & Conditions
  • Sitemap

© 2026 codingstuff.io. All rights reserved.

Built with ❤️ for developers everywhere

/
/
All Subjects
🗄️

DBMS

23 chapters

1Intro & 3-Schema Architecture2ER Model & Diagrams3Generalization, Specialization & Aggregation4Relational Model & Codd's Rules5Relational Algebra6Tuple & Domain Relational Calculus7SQL: DDL, DML, DCL8Advanced SQL (Joins, Aggregates)9Views, Triggers & Stored Procedures10Functional Dependencies11Normalization (1NF, 2NF, 3NF)12BCNF & Lossless Decomposition13Transaction Concepts & ACID14Conflict & View Serializability15Concurrency Control & Locks162-Phase Locking (2PL)17Timestamp-Based Protocols18Indexing (Primary, Clustering)19B-Trees & B+ Trees20Hashing Techniques in DBMS21Database Recovery Techniques22NoSQL Databases Overview23Data Warehousing Concepts
SubjectsDBMS

NoSQL Databases Overview

Updated 2026-04-29
2 min read

NoSQL Databases Overview

NoSQL (Not Only SQL) databases emerged in the late 2000s to address the limitations of traditional relational databases when dealing with massive-scale web applications (Facebook, Google, Amazon) that required handling billions of records, thousands of concurrent users, and flexible, evolving data schemas.

1. Key-Value Stores

The simplest NoSQL model. Data is stored as a collection of key-value pairs, like a giant hash map.

  • Get(key), Put(key, value), Delete(key).
  • No queries on values—you can only look up by key.
  • Examples: Redis (in-memory, used for caching), Amazon DynamoDB, Riak.
  • Use Case: Session management, shopping carts, user preferences, real-time leaderboards.

2. Document Stores

Data is stored as JSON-like documents. Each document can have a completely different structure (schema-less). Documents can contain nested objects and arrays.

  • Examples: MongoDB, CouchDB, Firebase Firestore.
  • Use Case: Content management systems, product catalogs with varying attributes, user profiles.

3. Wide-Column Stores

Data is stored in tables, but each row can have a different set of columns. Columns are grouped into column families. Optimized for reading and writing large volumes of data across many servers.

  • Examples: Apache Cassandra, HBase, Google Bigtable.
  • Use Case: Time-series data (IoT sensors), event logging at massive scale, recommendation engines.

4. Graph Databases

Data is represented as nodes (entities) and edges (relationships). Optimized for traversing complex relationships.

  • Examples: Neo4j, Amazon Neptune, ArangoDB.
  • Use Case: Social networks (friend-of-a-friend), fraud detection, knowledge graphs, recommendation engines.

5. The CAP Trade-off in NoSQL

Most NoSQL databases sacrifice strong consistency for availability and partition tolerance (AP systems). They provide Eventual Consistency: after a write, all replicas will eventually converge to the same value, but reads immediately after the write might return stale data. This is acceptable for many use cases (like a social media likes count being temporarily off by a few).



PreviousDatabase Recovery TechniquesNextData Warehousing Concepts

Recommended Gear

Database Recovery TechniquesData Warehousing Concepts