Database debates often begin with product names. They should begin with questions: what must be stored, how will it be queried, what can be rebuilt, and what must never be lost?
Start with access patterns
List the reads, writes, relationships, and consistency expectations your product actually has. A relational database is a powerful default because it makes data integrity explicit, not because every problem is relational.
Price the operations
Teams underestimate the cost of backups, migrations, monitoring, and incident response. A familiar system with strong tooling can beat a theoretically perfect choice that nobody on the team knows how to operate.
Choose the simplest system that keeps important promises. You can add complexity when the evidence arrives.