**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....
The complete answer continues with detailed implementation patterns, architectural trade-offs, and production-grade considerations. It covers performance optimization strategies, common pitfalls to avoid, and real-world examples from companies like Chryselys. The answer also includes follow-up discussion points that interviewers commonly explore.
Continue Reading the Full Answer
Unlock the complete expert answer with code examples, trade-offs, and pro tips - plus 1,863+ more.
Or upgrade to Platform Pro - $39
Engineers who used these answers got offers at
AmazonDatabricksSnowflakeGoogleMeta
According to DataEngPrep.tech, this is one of the most frequently asked Spark/Big Data interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.