Reviewed by Aditya Kumar · Last reviewed 2026-03-25
**Derby**: Embedded, file-based. Zero config. Single-user. Dev/demo only. **Why Not Production**: No concurrency. Not for multi-user. Single point of failure. **Production Alternatives**: MySQL, PostgreSQL, Oracle. Configure javax.jdo.option.ConnectionURL. Shared metastore;...
Derby: Embedded, file-based. Zero config. Single-user. Dev/demo only.
Why Not Production: No concurrency. Not for multi-user. Single point of failure.
Production Alternatives: MySQL, PostgreSQL, Oracle. Configure javax.jdo.option.ConnectionURL. Shared metastore; connection pooling.
Why: Concurrent Hive/Spark sessions. HA. Backup.
Scalability Trade-offs: External DB scales. Connection pool size.
Cost Implications: RDS/Cloud SQL for managed. Self-managed = ops cost.
Pro-Move: 'PostgreSQL for Hive metastore; connection pool 20; HA.' Red Flag: Derby in prod—single user, no concurrency.
According to DataEngPrep.tech, this is one of the most frequently asked Spark/Big Data interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.