Developer Documentation

Database Partitioning Plan

Partitioning is prepared but not automatically applied. MySQL partitioning has strict rules around unique keys and foreign keys, so production rollout must be rehearsed on a restored backup.

Candidate Tables

transactions: monthly partitions by created_at
ledger_entries: monthly partitions by created_at
audit_logs: monthly partitions by created_at
request_logs: monthly partitions by created_at
webhook_events: monthly partitions by created_at

Optional Scripts

database/optional/partition_transactions.sql
database/optional/partition_ledger_entries.sql
database/optional/partition_audit_logs.sql

Rollout Plan

1. Confirm MySQL/MariaDB version and partitioning support.

2. Restore the latest production backup into staging.

3. Run optional partition script against staging.

4. Validate inserts, unique constraints, foreign keys, and query plans.

5. Benchmark dashboard, monitoring, and transaction history endpoints.

6. Schedule production migration during maintenance only.

Keep recent partitions hot and archive old partitions to cheaper storage after regulatory retention is defined.