subsystem-summary-of-database

The Stellar Core database subsystem manages schema migrations via versioning and handles connections through pooling for worker threads. It details key classes like Database and session_wrapper to coordinate these persistence tasks efficiently.

The dual-database approach in Stellar Core splits data between main and misc databases for SQLite. This architecture separates core operational data from miscellaneous data to streamline persistence and data management.

To understand the database architecture in Stellar Core, review the technical summary of its database subsystem. It details the single-database approach for PostgreSQL, key components like StatementContext, and data migration utilities for quick onboarding.

Stellar Core uses schema versioning for both PostgreSQL and SQLite, but their architectures differ. PostgreSQL uses a single-database approach, while SQLite splits data across main and misc databases, each with its own schema management.

The Stellar Core database subsystem provides data migration and pruning utilities to manage database size and history. These tools work alongside schema versioning to maintain data integrity across both SQLite and PostgreSQL deployments.

Stellar Core uses a single-database approach for PostgreSQL instead of the dual-database split used for SQLite. This design choice aligns with PostgreSQL's robust connection pooling and concurrent transaction handling capabilities for worker threads.