RightMV
← System overview

STORAGE / COMMUNITY

MapDB

A practical embedded storage option for lightweight local and single-server systems.

01 / DESIGN

How MapDB stores data.

MapDB keeps each account and logical file in an embedded local store beneath the configured data root. DATA and DICT areas remain separate, commits are handled by the embedded database, and no external database service is required.

AVAILABILITYCommunity storage provider.
  1. 01BASIC file operation
  2. 02Storage file adapter
  3. 03Embedded MapDB file
  4. 04Local filesystem

02 / TRADE-OFFS

Choose the engine for the workload.

Storage engines balance memory, I/O, recovery, concurrency and operational complexity. These profiles show where each engine fits.

STRENGTHS

  • Simple installation and backup model
  • Low operational overhead
  • Good fit for local and single-server use
  • Familiar account and file directory layout

WEAKNESSES

  • Scaling and concurrency remain tied to one host
  • Many logical files create many embedded stores
  • Not intended for clustered database operations
  • Secondary-index features depend on the provider surface

03 / ABILITIES

What it provides.

MapDB provides an embedded storage path that keeps deployment straightforward and ships alongside UberHash in Community Edition.

01

Per-account file layout

02

Case-insensitive account and file resolution

03

Atomic account-directory rename where supported

04

Normal export and import portability

BEST FIT

  • Local development
  • Learning environments
  • Embedded deployments
  • Single-server systems

CORE CAPABILITIES

  • Embedded operation
  • ExecutionContext storage integration
  • No separate database service
  • Portable development environments

CONFIGURATION

  • MVDB_MAPDB_DATA_ROOT
  • MVDB_PERF_SLOW_MS