Database / BetterDB Interview questions
Why does BetterDB Monitor need PostgreSQL for production deployments?
The Docker image only bundles the monitoring application itself – the backend API and frontend – not a database to remember anything in.
The default memory storage mode is explicitly a testing/ephemeral option: every slowlog, client-analytics record, capture, and anomaly baseline is lost when the container restarts.
For a production deployment you want that history to survive restarts and upgrades, so BetterDB is designed to hand persistence off to postgres (STORAGE_TYPE=postgres + STORAGE_URL) or, for a serverless setup, turso.
sqlite is deliberately left out of the equation here too, since its native module is stripped from the Docker image and it's meant for local development instead.
What happens to data in 'memory' storage mode when the container restarts?
Why can't you use sqlite storage inside the standard Docker image?
More Related questions...
