liveBook · Manning

In-memory database

An in-memory database is a database whose primary working data resides in main memory rather than primarily in persistent storage.

How 5 Manning books explain it

Amazon Web Services in Action, Third Edition: An in-depth guide to AWS

An in-memory data store keeps data primarily in volatile memory to provide low-latency reads and writes.

How it is used
Positions an in-memory layer between applications and primary databases to reduce read pressure and serve low-latency game or forum data.
How deep it goes
Works through a minimal CloudFormation cluster and deployment choices, but leaves cache-freshness techniques at a summary level.
Examples
Uses a Redis game leaderboard, game sessions, and a Discourse deployment with PostgreSQL and Redis.
What you can do after
Operate/configure a basic ElastiCache cluster with CloudFormation and evaluate engine and deployment options against persistence and availability needs.

Read how Amazon Web Services in Action, Third Edition: An in-depth guide to AWS explains in-memory database →

ASP.NET Core in Action, 3e

An in-memory database provider is a database-provider implementation that stores test data in process memory instead of persistent database storage.

How it is used
Supports fast, isolated tests for services that depend on an EF Core DbContext without requiring a real database.
How deep it goes
Descends from provider comparison to SQLite connection setup, schema creation, data seeding, context reuse, and connection-lifetime behavior.
Examples
Uses RecipeService, Recipe entities, SQLite connections, EnsureCreated(), and assertions against a loaded recipe view model.
What you can do after
Apply it via EF Core to test DbContext-dependent services with isolated in-memory data and controlled database setup.

Read how ASP.NET Core in Action, 3e explains in-memory database →

Build and Orchestrator in Go (From Scratch)

An in-memory store is a storage implementation that keeps its data in volatile memory rather than persistent storage.

How it is used
Supplies development-time task and event storage behind a shared Store interface for an orchestrator.
How deep it goes
Implements typed map-backed event storage and traces manager refactoring to Get, Put, and List calls.
Examples
Demonstrates task-event map storage, manager datastore selection, typed Get results, Put updates, and List-based task retrieval.
What you can do after
Build it from scratch as typed map-backed task and event stores selected through a Store interface.

Read how Build and Orchestrator in Go (From Scratch) explains in-memory database →

Kafka Streams in Action, Second Edition

An in-memory state store keeps its contents in process memory and loses them when the application shuts down.

How it is used
Selects a fast, memory-resident store for stateful Kafka Streams operations such as reductions, aggregations, and joins.
How deep it goes
Explains memory, changelog restoration, capacity limits, naming, and Java configuration, but defers detailed store variants.
Examples
Demonstrates an online poker-game score reduction using Stores.inMemoryKeyValueStore and Materialized.
What you can do after
Build it from scratch by configuring and naming an in-memory Kafka Streams store with Java APIs.

Read how Kafka Streams in Action, Second Edition explains in-memory database →

Rust Servers, Services, and Apps

An in-memory data store is a data-storage component that keeps its working data in main memory rather than relying primarily on persistent storage.

How it is used
Supports course REST APIs with a thread-safe store instead of a database.
How deep it goes
Shows a mutex-protected course vector in application state and its empty initialization.
Examples
Uses an initially empty Mutex<Vec<Course>> as the course store.
What you can do after
Build it from scratch as shared Actix state containing a mutex-protected course collection.

Read how Rust Servers, Services, and Apps explains in-memory database →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.