Skip to content
BlazorSaas Documentation

MartenDB

MartenDB delivers reliable data storage for BlazorSaas using PostgreSQL. It integrates tightly with .NET and powers the template’s persistence layer.

Why We Use It

BlazorSaas uses MartenDB to manage data efficiently and reduce setup overhead. It taps into PostgreSQL’s robustness while keeping configuration straightforward. This ensures dependable storage with minimal effort.

How We Use It

MartenDB manages data in BlazorSaas through document sessions for simple operations, batch queries for reducing chattiness, and compiled queries for increased performance.

The setup-env Nuke target configures it by prompting for database credentials during initial setup.

The code target generates supporting code for MartenDB, stored in the internal directory. This directory can be deleted after breaking changes but should stay in source control.

Schema updates rely on these Nuke targets:

  • initial-migration: Generates initial migration scripts (triggered by setup-env).
  • patch-migration: Creates scripts for changes since the latest migration.
  • apply-migrations: Applies all migration scripts to the current database.

Database versioning uses MinVer with Git tags to track schema changes. Run initial-migration or patch-migration, tag the commit (e.g., v1.0.0), then use apply-migrations locally. On deployment, BlazorSaas applies all migration scripts automatically. Check the repository to review script changes.

How It Scales

MartenDB supports extending its role to event sourcing when needed. This capability allows BlazorSaas to record data changes as events, supporting advanced features like auditing or state tracking. Enable it as your application’s complexity grows.

Resources