I agree and disagree. As an operation person, I think we need to make an argument for why X can&#x27;t be done right away, but we must have a plan Y for migration. I know for a fact there is still some ancient database server running in our data center serving our critical business but there&#x27;s a plan to migrate that to modern databases. While re implementing everything is costly, company has to hire specialist from a specific consulting firm to support such ancient database, and how long can we retain such talent without spending extreme amount and caution? &quot;I am scared if I did this will screw everything up.&quot; There will be a point they have to migrate such database to something modern, and the cost is still several million plus.<p>The same argument that corporate world doesn&#x27;t allow Python 3 or has a hard time to migrate to Python 3 because machines are running on some ancient RHEL servers or because of some security requirement. I get it and I don&#x27;t get it. First, let&#x27;s ditch RHLE. Fuck that. I really don&#x27;t see reason to use RHLE; fine, YMMV. But it is people&#x27;s job to do work. Some pieces can die, and some pieces will have to evolve, either from scratch, or slowly. No one said software development and operation support are easy, see <a href="https:&#x2F;&#x2F;pbs.twimg.com&#x2F;media&#x2F;CWC74tOVAAAsls0.jpg:large" rel="nofollow">https:&#x2F;&#x2F;pbs.twimg.com&#x2F;media&#x2F;CWC74tOVAAAsls0.jpg:large</a>.