Nah. MySQL rocks. I&#x27;ve been using it since 1998 at Credit Suisse, 2000 at eToys.com where we used it to run the entire company from warehouse to web. I used it at the BBC in 2003 for a high traffic Radio 1 application and I&#x27;ve used it since then on my own companies with serious volume including a job search engine featured in NYTimes and Time Mag in 2005 and feedjit.com doing real-time traffic on over 700,000 sites. We use it for Wordfence now which is where the image link comes from I posted earlier with 20K TPS. All very high traffic with consequences if it screws up. I&#x27;ve never run into any of the issues you mention.<p>You say &quot;upserting into a mysql table&quot;. Which storage engine? MyISAM? InnoDB? I find MySQL to be both reliable and incredible durable i.e. it handles yanking the power cord quite well. The performance also scales up linearly for InnoDB even for very high traffic and concurrency applications.<p>We use redis, memcached and other storage engines - by no means are we tied to mysql. But for what it does, it does it incredibly well.<p>I&#x27;m also completely open to using PostgreSQL and I was hoping someone could give me a compelling reason to switch to it or to use it.