&gt; I consider MySQL a red flag and avoid any projects or teams that choose it over Postgres.<p>I am in the &quot;pro Postgres&quot; camp, but this attitude is too black and white for me. For many projects Postgres in superior to MySQL, but there are situations and requirements where MySQL makes a lot more sense.<p>For just one example, I can get MySQL as a service much cheaper and easier than I can get Postgres as a service. Which isn&#x27;t to say Postgres as a service doesn&#x27;t exist (it does), just to say MySQL is more readily available and there is more competition in that sector.<p>Additional if I had a DBA who was a MySQL expert and didn&#x27;t know a thing about Postgres, I&#x27;d go with MySQL for my project. Since a good DBA is worth their weight in gold, and an expert in a particular DBMS can be a massive asset to a project.<p>But given no restrictions or needs, I&#x27;d pick Postgres as my &quot;default&quot; choice. I just don&#x27;t think it is right to say you&#x27;d avoid a team&#x2F;project just because they picked MySQL, sometimes there are completely legit reasons (or politics).