"Right tool for the job" is as foolish as any other approach: this discounts the experience someone or even a team might have with another tool that is not a pe

"Right tool for the job" is as foolish as any other approach: this discounts the experience someone or even a team might have with another tool that is not a perfect fit, but might still do the job just as well. If you ignore this and instead go with a different tool for every little thing, your project will be a dependency nightmare no developer can master easily. Postgres is an all-purpose database that has it all: relational databases were created to model real world problems, and while they might not perform best for all the usecases, they can usually model them just fine while protecting from many programming errors. And then Postgres has features on top: partial indexes, object DB features, replication etc.