Question: What is the difference between key-value and document databases?


Key-value and document databases are both types of NoSQL databases designed to handle large volumes of data, but they differ significantly in terms of their structure, use cases, and the kind of queries they support. Understanding these differences is crucial for selecting the right database for your project.

Key-Value Databases

Structure: In a key-value database, data is stored as a collection of key-value pairs, where each key is unique, and is used to retrieve the corresponding value. The value is typically opaque to the database, meaning the database doesn't understand its internal structure.

Use Cases: They are ideal for scenarios requiring fast lookups, where the access pattern is well-known and simple. Use cases include caching, session storage, and settings or preferences storage.

Examples: Redis, DynamoDB

Example Code for Redis (Python)

import redis # Connect to Redis r = redis.Redis(host='localhost', port=6379, db=0) # Set a key-value pair r.set('foo', 'bar') # Get the value by key value = r.get('foo') print(value) # Output: b'bar'

Document Databases

Structure: Document databases store data in documents (often JSON, BSON, etc.), which allows for a more complex structure compared to the simple key-value pairs. Each document can contain nested structures like arrays and sub-documents.

Use Cases: These databases are suitable for storing and querying data with a flexible schema. Use cases include content management systems, e-commerce applications, and any scenario where each data entity contains many different attributes that may vary across entities.

Examples: MongoDB, Couchbase

Example Code for MongoDB (Python)

from pymongo import MongoClient # Connect to MongoDB client = MongoClient('mongodb://localhost:27017/') # Select Database db = client.example_database # Select Collection collection = db.example_collection # Insert a document collection.insert_one({'name': 'John Doe', 'age': 30}) # Query a document person = collection.find_one({'name': 'John Doe'}) print(person)


  • Schemas: Key-value stores usually don't care about the schema of the value, whereas document databases allow and sometimes require a semi-structured schema.
  • Query Capabilities: Document databases typically offer richer query capabilities, allowing for searches within the contents of the documents, unlike key-value stores where you generally can only query by the key.
  • Data Complexity: Document databases better handle complex data and relationships within the data compared to key-value databases which are more suited for simpler datasets.

Choosing between a key-value and a document database largely depends on the requirements of your application, including the complexity of the data you're dealing with, the types of queries you need to perform, and how much flexibility you need in terms of schema design.

Was this content helpful?

White Paper

Free System Design on AWS E-Book

Download this early release of O'Reilly's latest cloud infrastructure e-book: System Design on AWS.

Free System Design on AWS E-Book

Start building today

Dragonfly is fully compatible with the Redis ecosystem and requires no code changes to implement.