liveBook · Manning

Embedded database

An embedded database is a database engine integrated into and running within the same process or runtime as the application that uses it.

How 2 Manning books explain it

Latency

An embedded database is a database engine that runs in the same process or memory space as the application using it.

How it is used
Deploys database access inside a Rust REST API to reduce request latency and measure colocation’s performance effect.
How deep it goes
Descends through connection setup, request handling, benchmarking, and latency distributions, but does not develop database internals.
Examples
Uses a SQLite-backed /hello endpoint, direct SQL queries, wrk output, and an eCDF comparing SQLite with PostgreSQL.
What you can do after
Apply it via Rust, Actix Web, SQLite, and wrk to build and measure a colocated database-backed endpoint.

Read how Latency explains embedded database →

Spring in Action, Sixth Edition

An embedded database is a database engine that runs within the application process or development environment rather than as a separately managed service.

How it is used
Supports local development and testing without a separately running database service.
How deep it goes
Explains dependency and configuration choices, then defers production deployment to external database properties.
Examples
Uses Flapdoodle embedded MongoDB and H2 in-memory databases, including fixed H2 naming for console connections.
What you can do after
Configure an embedded MongoDB or H2 database for development and testing, then point Spring Data MongoDB at production infrastructure.

Read how Spring in Action, Sixth Edition explains embedded 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.