Specialized & Multi-Model Databases
Go beyond relational and columnar engines: twelve database families, from document, key-value, graph, and time-series to vector, search, NewSQL, and multi-model, each with a distinct enterprise use case and an end-to-end prototype you build.
The full syllabus, family by family
Each of the 12 database families has its own twenty-lesson path in four modules, grounded in a distinct enterprise use case and building an end-to-end prototype. Expand any module to see its lessons.
Document Databases 20 lessons · MongoDB, Couchbase
Store data as flexible JSON or BSON documents rather than rows and columns, so each record carries a nested, evolving shape without a fixed schema.
Enterprise use case: a product-catalog and order service for a retailer, where every product has different attributes and orders embed line items, addresses, and status history in one document.
M1 The document model Ch 1-5 · 5 chapters
- Why documents, and when to choose them
- Documents, collections, and databases
- JSON and BSON, and data types
- Setting up the catalog project
- Modeling the first product document
M2 Modeling and querying Ch 6-10 · 5 chapters
- Embedding versus referencing
- CRUD operations
- Query operators and filtering
- Indexing documents
- Modeling orders with embedded items
M3 Aggregation and analytics Ch 11-15 · 5 chapters
- The aggregation pipeline
- Grouping and computing metrics
- Joining collections
- Building the reporting layer
- Optimizing aggregation performance
M4 Scale, operations, and the prototype Ch 16-20 · 5 chapters
- Replication and replica sets
- Sharding for scale
- Transactions and consistency
- Securing and operating the store
- Shipping the catalog-and-orders service
Key-Value Databases 20 lessons · Redis, Amazon DynamoDB
Store data as simple key-value pairs for extremely fast reads and writes, trading rich query power for raw speed and predictable low latency.
Enterprise use case: a session store and rate limiter for a high-traffic web platform, where millions of lookups per second must return in well under a millisecond.
M5 The key-value model Ch 21-25 · 5 chapters
- Why key-value, and its latency profile
- Keys, values, and namespaces
- Values and data structures
- Setting up the platform project
- First reads and writes
M6 Access patterns Ch 26-30 · 5 chapters
- Designing keys
- Expiry and eviction
- Caching patterns
- Building the session store
- Atomic operations and counters
M7 Building the rate limiter Ch 31-35 · 5 chapters
- Rate-limiting algorithms
- Implementing a counter-based limiter
- Avoiding hot keys
- Testing under load
- Integrating the limiter into the app
M8 Persistence, scale, and the prototype Ch 36-40 · 5 chapters
- Persistence options
- Replication and high availability
- Partitioning and clustering
- Monitoring latency and throughput
- Shipping the session-store and limiter
Wide-Column Databases 20 lessons · Apache Cassandra, Apache HBase
Organize data into rows with dynamic, wide sets of columns, optimized for writing and reading enormous volumes across a distributed cluster with no single point of failure.
Enterprise use case: a time-ordered event and messaging store for a large consumer app, ingesting billions of writes per day across many data centers with always-on availability.
M9 The wide-column model Ch 41-45 · 5 chapters
- Why wide-column, and its scale story
- Keyspaces, tables, and columns
- The distributed, masterless design
- Setting up the messaging project
- Query-first thinking
M10 Modeling for the cluster Ch 46-50 · 5 chapters
- Partition keys
- Clustering columns and ordering
- Denormalization and table-per-query
- Modeling the event stream
- Modeling the message store
M11 Consistency and the write path Ch 51-55 · 5 chapters
- Replication across data centers
- Tunable consistency
- The write path and commit log
- The read path and compaction
- Handling high write volume
M12 Operations, scale, and the prototype Ch 56-60 · 5 chapters
- Cluster topology and nodes
- Adding and removing nodes
- Monitoring and repair
- Multi-data-center operations
- Shipping the event-and-messaging store
Graph Databases 20 lessons · Neo4j, Amazon Neptune
Store entities as nodes and relationships as edges, making it natural and fast to traverse deep, interconnected relationships that would be costly joins in a relational database.
Enterprise use case: a fraud-detection and recommendation graph for a bank, linking customers, accounts, devices, and transactions to surface rings and suspicious patterns in real time.
M13 The graph model Ch 61-65 · 5 chapters
- Why graphs, and where they win
- Nodes, edges, and properties
- Graph versus relational joins
- Setting up the fraud project
- Modeling the first entities
M14 Querying the graph Ch 66-70 · 5 chapters
- A graph query language
- Pattern matching
- Traversals and variable-length paths
- Modeling transactions as edges
- Querying suspicious patterns
M15 Graph algorithms Ch 71-75 · 5 chapters
- Pathfinding and shortest paths
- Centrality and influence
- Community detection
- Similarity for recommendations
- Building the recommendation layer
M16 Scale, real-time, and the prototype Ch 76-80 · 5 chapters
- Indexing and query performance
- Scaling large graphs
- Real-time fraud scoring
- Operating the graph store
- Shipping the fraud-and-recommendation graph
Time-Series Databases 20 lessons · InfluxDB, TimescaleDB
Optimize for timestamped measurements written in order and queried over time windows, with efficient storage, retention, and downsampling of high-frequency data.
Enterprise use case: an industrial sensor and metrics platform for a manufacturer, ingesting readings from thousands of machines and serving live dashboards and alerts.
M17 The time-series model Ch 81-85 · 5 chapters
- Why time-series, and its workload
- Measurements, tags, and fields
- Storage and compression for time data
- Setting up the sensor project
- Writing the first measurements
M18 Ingesting at scale Ch 86-90 · 5 chapters
- High-frequency ingestion
- Batching and write efficiency
- Handling out-of-order and late data
- Modeling the sensor fleet
- Validating incoming data
M19 Querying over time Ch 91-95 · 5 chapters
- Time-window queries
- Downsampling and rollups
- Continuous aggregates
- Retention policies
- Building the metrics queries
M20 Dashboards, alerts, and the prototype Ch 96-100 · 5 chapters
- Connecting a dashboard tool
- Building live dashboards
- Threshold and anomaly alerts
- Scaling and operating the platform
- Shipping the sensor-and-metrics platform
Object-Oriented Databases 20 lessons · ObjectDB, db4o
Persist application objects directly, preserving their structure and relationships without an object-relational mapping layer, so complex object graphs are stored and retrieved as-is.
Enterprise use case: a CAD and engineering-model store for a design firm, where deeply nested object structures must be saved and reloaded with full fidelity and no mapping overhead.
M21 The object database model Ch 101-105 · 5 chapters
- Why object databases exist
- Objects, classes, and persistence
- The impedance mismatch problem
- Setting up the engineering project
- Persisting the first objects
M22 Storing object graphs Ch 106-110 · 5 chapters
- Relationships between objects
- Deeply nested structures
- Identity and equality
- Modeling the CAD domain
- Round-tripping a model
M23 Querying and transactions Ch 111-115 · 5 chapters
- Querying objects directly
- Navigating object relationships
- Transactions and the object lifecycle
- Concurrency and locking
- Versioning stored objects
M24 Fit, operations, and the prototype Ch 116-120 · 5 chapters
- Performance characteristics
- When object databases fit
- Backups and operations
- Migration considerations
- Shipping the engineering-model store
Columnar (Analytical) Databases 20 lessons · ClickHouse, Amazon Redshift, Snowflake
Store data by column rather than by row, so analytical queries scan only the columns they need and compress heavily, delivering fast aggregations over huge datasets.
Enterprise use case: a business-intelligence warehouse for a retailer, aggregating billions of sales rows into sub-second dashboards across products, regions, and time.
M25 Columnar foundations Ch 121-125 · 5 chapters
- Why columnar, and where it wins
- Row versus column storage
- Compression and encoding
- Setting up the warehouse project
- Loading the first analytical data
M26 Modeling for analytics Ch 126-130 · 5 chapters
- Sort keys and data layout
- Dimensional modeling
- Partitioning large tables
- Modeling the sales schema
- Loading at scale
M27 Fast aggregation Ch 131-135 · 5 chapters
- Aggregations and roll-ups
- Materialized views
- Query optimization
- Building the dashboard queries
- Caching and concurrency
M28 Cost, operations, and the prototype Ch 136-140 · 5 chapters
- Performance tuning
- Cost control
- Operating the warehouse
- Connecting a BI tool
- Shipping the BI warehouse
NewSQL Databases 20 lessons · CockroachDB, Google Cloud Spanner
Combine the familiar relational model and strong transactional guarantees with the horizontal, distributed scalability usually associated with NoSQL systems.
Enterprise use case: a globally distributed ledger for a payments company, requiring strongly consistent transactions across regions without giving up SQL or ACID.
M29 The NewSQL model Ch 141-145 · 5 chapters
- Why NewSQL exists
- Distributed SQL versus NoSQL
- The relational model, distributed
- Setting up the ledger project
- First distributed tables
M30 Distributed transactions Ch 146-150 · 5 chapters
- Strong consistency across nodes
- Distributed transaction protocols
- Isolation and correctness
- Modeling the ledger schema
- Implementing money movement
M31 Data distribution Ch 151-155 · 5 chapters
- Ranges, shards, and rebalancing
- Data locality and placement
- Global tables and multi-region
- Handling region failures
- Modeling multi-region ledgers
M32 Operations, scale, and the prototype Ch 156-160 · 5 chapters
- Deploying a cluster
- Scaling out
- Monitoring and resilience
- Backups and disaster recovery
- Shipping the distributed ledger
In-Memory Databases 20 lessons · SAP HANA, Redis
Keep data primarily in RAM rather than on disk, delivering ultra-low latency for both transactions and analytics where speed matters more than storage cost.
Enterprise use case: a real-time pricing and risk engine for a trading desk, recomputing positions and exposure in memory as market data streams in.
M33 The in-memory model Ch 161-165 · 5 chapters
- Why in-memory, and its latency edge
- Memory versus disk data structures
- The cost and capacity trade-off
- Setting up the pricing project
- First in-memory reads and writes
M34 In-memory processing Ch 166-170 · 5 chapters
- In-memory transactions
- In-memory analytics
- Streaming input
- Modeling positions and exposure
- Recomputing on the fly
M35 Durability and capacity Ch 171-175 · 5 chapters
- Persistence for in-memory data
- Recovery after restart
- Memory management
- Capacity planning
- Eviction and tiering
M36 Availability and the prototype Ch 176-180 · 5 chapters
- Replication for in-memory stores
- High availability and failover
- Monitoring latency
- Operating the engine
- Shipping the pricing-and-risk engine
Vector Databases 20 lessons · Milvus, Pinecone, Weaviate
Store high-dimensional embedding vectors and search them by similarity, powering semantic search, recommendations, and retrieval-augmented generation for AI applications.
Enterprise use case: a semantic search and retrieval layer for a company knowledge base, letting an AI assistant answer questions grounded in the organization's own documents.
M37 Vectors and embeddings Ch 181-185 · 5 chapters
- Why vector databases, and where they fit
- Embeddings and vector space
- Distance and similarity metrics
- Setting up the knowledge-base project
- Storing the first vectors
M38 Indexing and search Ch 186-190 · 5 chapters
- Approximate nearest neighbor
- Index types and trade-offs
- Embedding documents
- Similarity queries
- Filtering with metadata
M39 Retrieval-augmented generation Ch 191-195 · 5 chapters
- The RAG pattern
- Chunking and preparing documents
- Building the retrieval step
- Wiring retrieval into the assistant
- Evaluating answer quality
M40 Scale, operations, and the prototype Ch 196-200 · 5 chapters
- Scaling vector search
- Tuning recall and latency
- Updating and re-embedding
- Operating the vector store
- Shipping the semantic-search assistant
Search Databases 20 lessons · Elasticsearch, OpenSearch
Index text for fast full-text search, ranking, filtering, and aggregation, so applications can search large document and log collections with relevance scoring and near-real-time results.
Enterprise use case: a product search and log-analytics platform for an online store, powering typo-tolerant product search and real-time operational dashboards over application logs.
M41 Search foundations Ch 201-205 · 5 chapters
- Why search engines, and where they fit
- The inverted index
- Analyzers, tokens, and terms
- Setting up the search project
- Indexing the first documents
M42 Querying and relevance Ch 206-210 · 5 chapters
- Full-text queries
- Relevance scoring
- Typo tolerance and fuzzy search
- Filters and faceted search
- Building product search
M43 Aggregations and log analytics Ch 211-215 · 5 chapters
- Aggregations and facets
- Ingesting logs
- Time-based log queries
- Building log dashboards
- Near-real-time analytics
M44 Scale, operations, and the prototype Ch 216-220 · 5 chapters
- Shards and replicas
- Cluster operations
- Index lifecycle management
- Tuning relevance and performance
- Shipping the search-and-logs platform
Multi-Model Databases 20 lessons · ArangoDB, Azure Cosmos DB
Support several data models, document, graph, key-value, and more, within a single engine, so one system can serve varied workloads without stitching together many databases.
Enterprise use case: a unified customer-360 platform for an enterprise, combining document profiles, a relationship graph, and key-value preferences in one database.
M45 The multi-model idea Ch 221-225 · 5 chapters
- Why multi-model, and when it helps
- The models it combines
- One engine versus many databases
- Setting up the customer-360 project
- Choosing a model per workload
M46 Documents and key-value Ch 226-230 · 5 chapters
- Document profiles
- Key-value preferences
- Modeling the customer profile
- Querying documents and keys
- Indexing across models
M47 The relationship graph Ch 231-235 · 5 chapters
- Graph relationships
- Traversing the customer graph
- Combining graph with documents
- Building the unified view
- Cross-model queries
M48 Design, trade-offs, and the prototype Ch 236-240 · 5 chapters
- Designing a unified platform
- Consistency across models
- Trade-offs versus specialized stores
- Operating a multi-model store
- Shipping the customer-360 platform
Three ways to take Specialized and Multi-Model Databases
| Feature | Self-paced | Cohort | Enterprise |
|---|---|---|---|
| Format | Written chapters, video explainers and podcasts | Everything in self-paced, plus scheduled live sessions | Everything in cohort, delivered privately to your team |
| Live sessions | None | Scheduled, instructor-led | Scheduled, instructor-led, private |
| Mentorship | Not offered | Not offered | Not offered |
| Access | Lifetime | Lifetime | Lifetime for every enrolled seat |
| Pace | Entirely your own | Guided schedule with a peer group | Agreed with your desk |
| Tailoring | Fixed curriculum | Fixed curriculum | Sequenced to your markets, systems and governance |
| Best for | Individuals learning around a job | Individuals who want structure and deadlines | Desks building the same capability together |
Get the programme guide
The full chapter list, what each module covers, and how the tiers compare - sent to your inbox as a PDF.
Run this for my desk
Private delivery for your desk, sequenced to your markets and systems. Tell us the team and we will scope it.
Run this for my deskFrequently asked questions
What is the Specialized & Multi-Model Databases programme?
Go beyond relational and columnar engines: twelve database families, from document, key-value, graph, and time-series to vector, search, NewSQL, and multi-model, each with a distinct enterprise use case and an end-to-end prototype you build.
Who is this programme for?
It suits engineers who want the full database landscape, along with others described on this page.
How is it delivered?
Self-paced with hands-on labs; twelve families, twenty lessons each, twelve prototypes.
Is there a project or capstone?
Across twelve database families you build twelve end-to-end prototypes, each grounded in a distinct enterprise use case, from a retailer's catalog service and a bank's fraud graph to a sensor platform, a distributed ledger, a semantic-search assistant, and a customer-360 store, so you learn not just how each database works but exactly when to reach for it.
How does this fit the wider journey?
This programme closes the databases stage by going broad rather than deep, complementing the single-engine programmes. The ability to choose the right database for a workload is a hallmark of the senior and principal roles the whole track builds toward.
Can my organization run this as a private cohort?
Yes. Every programme can be delivered as a tailored corporate cohort. Contact us to scope it.