liveBook · Manning

NoSQL database

As explained in Building Distributed Applications that Work

A non-relational database system that stores and accesses data using models other than relational tables and does not rely primarily on SQL.

NoSQL describes storage that does not rely primarily on SQL or standard relational tables and relationships. It does not mean that a database cannot use SQL. NoSQL has no shared database type or standard, and systems within the same category can work differently. section 3.6

Choose a model to suit the workload:

  • Document stores, such as MongoDB and Couchbase, suit frequently retrieved complex data when entity relationships matter less. section 3.6
  • Key-value stores, such as Redis and DynamoDB, suit distributed caches where fast retrieval matters most. section 3.6
  • Graph databases, such as Neo4j and ArangoDB, represent connections and suit maps of relationships such as social networks or supply chains. section 3.6
  • Column-family stores, such as Cassandra and HBase, allow columns to vary between rows and suit data warehousing. section 3.6

In Aspire, popular NoSQL databases and Azure-native storage services have integrations. Some Azure services can use emulators for local development. section 3.8

How Building Distributed Applications that Work covers it

How deep it goes
Defines NoSQL by its non-reliance on relational tables or SQL, distinguishes four models and their workloads, and stops short of setup details.
Examples
Illustrates four models with MongoDB, Redis, Neo4j, and Cassandra, and associates them with cache, warehousing, social, and logistics workloads.
What you can do after
Evaluate storage choices by matching key-value, column-family, graph, and document models to their stated workload strengths.
How it connects
Connects NoSQL to relational databases, SQL, document stores, key-value stores, graph databases, and column-family stores.

Also explained in

Compare how 7 books explain NoSQL database →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Building Distributed Applications that Work. The section links point to the parts of the book it draws on.