NoSQL Concepts
Compare key-value, document, column family and graph databases with relational ones, and learn when each NoSQL type fits a business need.
NoSQL databases store data differently from relational tables, and each of the main types suits different business requirements. The lessons set four models side by side: key-value, document, column-family and graph. They weigh what each does well and where it falls short, then show real companies that adopted Redis, MongoDB, Apache Cassandra and Neo4j to solve a specific business problem.
What You Will Achieve
- Explain how NoSQL databases differ from relational databases
- Identify the building blocks of documents, collections, column families and graphs
- Match a business requirement to the NoSQL type that suits it, and spot when a type is a poor fit
- Relate Redis, MongoDB, Apache Cassandra and Neo4j to the database type each one represents
Program Overview
NoSQL vs Relational and Key-Value Databases
Sets NoSQL apart from relational systems, then examines the simplest model, built on keys and values.
- Differences between NoSQL and relational databases
- Keys, values, strengths and limits
- When key-value storage is suitable
- Redis features and the Editoo case
Document and Column Family Databases
Two more models, each weighed for its advantages and limitations and tested against suitable and unsuitable use cases.
- Documents, collections and how they compare with key-value storage
- Column family components and their trade-offs
- MongoDB features, products and the Shutterfly case
- Cassandra features and the Bigmate case
Graph Databases and Neo4j
Closes with graph databases and a company that used Neo4j for better cost control.
- Graph database components
- Strengths, limits and appropriate use cases
- Neo4j features and graph platform
- The Gousto case study
Certificate Awarded (Paid)
Job Outlook
Knowing which NoSQL model fits a requirement helps in data engineering and database design work, where teams choose between relational and NoSQL storage for an application.
Good for: People who already work with relational databases and want a clear map of NoSQL options before choosing one for a project.
Keep in mind: It is conceptual, with no coding: you read, classify and judge use cases rather than query Redis, MongoDB, Cassandra or Neo4j yourself.
Bottom line: Pairing each NoSQL type with a named company case gives a practical frame for choosing a database without writing a line of code.
Frequently Asked Questions
Which companies serve as case studies?
Each chapter ends with one company: Editoo used Redis to reduce downtime and improve performance, Shutterfly used MongoDB to cut latency and reach market faster, Bigmate used Apache Cassandra for heavy concurrent traffic, and Gousto used Neo4j for better cost control.
Will I write queries or code during the lessons?
No. The exercises are conceptual: you classify advantages and limitations, answer true-or-false items, tell database types apart, and judge whether a use case is suitable or not for each model.
What does each chapter say about the database engines?
Every chapter has a lesson on the features of its engine, Redis, MongoDB, Cassandra or Neo4j. The MongoDB chapter also looks at its products, and the graph chapter at the Neo4j graph platform.


There are no reviews yet.