Relational Database Systems Are Becoming A Problem — But What To Do About It?
<p>My relationship with relational databases relates back to the late 90s. It was part of my first steps with computers and programming, became an essential part of my formal education and studies as a software engineer and constantly followed me through my professional career. I almost crawled through the entire RDBMS rabbit hole and still love it.</p>
<p><img alt="" src="https://miro.medium.com/v2/resize:fit:700/1*wHmRMm6XHD2vs_JRYbroYQ.png" style="height:329px; width:700px" /></p>
<p>“I’ll just stick with it” — the most common approach to databases?</p>
<p>During my career, I touched MySQL, Postgres, Oracle, Microsoft SQL Server, DBase, Access, SQLite, DB2, MariaDB, AWS RDS, Azure SQL, Google Cloud SQL and pretty much any RDBMS I could get my hands on. You can’t love RDBMS without loving SQL which is a rabbit hole of its own. And not all SQLs are the same. You’ve got MySQL with its own jargon, you’ve got Microsoft’s T-SQL and the world famous PL/SQL from Oracle. Probably not necessary to mention that they’re all not compatible with each other.</p>
<p><a href="https://medium.com/@jankammerath/relational-database-systems-are-becoming-a-problem-but-what-to-do-about-it-eb868d060601"><strong>Website</strong></a></p>