{"version":1,"type":"rich","provider_name":"Libsyn","provider_url":"https:\/\/www.libsyn.com","height":90,"width":600,"title":"The Cost of Multiple Platforms","description":"I ran into an interesting post that noted the modern data platform can have a bunch of different systems underlying it. The example might be that your "software" could use PostgreSQL, MongoDB, Cassandra, Clickhouse, and something NewSQL (Spanner, CockroachDB, etc,). Some of you might think that's not reality, but keep in mind that for a lot of your organizations, the "software" is what the customer uses. I'm sure my bank has multiple systems behind the mobile app I use to pay for things, move money, check balances, etc. I would guess there is some DB\/2, SQL Server, and some analytics or No\/NewSQL stuff in there. Hidden as different applications that make up the "app", but they are still in there from my perspective as a user of the app. No one intentionally designs software like this, but we still see it. They might not even have 5 or 6 platforms in their organization, but almost none of the customers I work with have less than 3. Somehow, somewhere, someone added a PostgreSQL server to an Oracle\/SQL Server environment. MongoDB crept in when someone thought it was a better store than DB\/2 or MySQL. An article written about how Facebook or Spotify or some other high tech company used Cassanda or Snowflake inspired a developer to add that to their toolbelt and build it into their application. Read the rest of The Cost of Multiple Platforms ","author_name":"Voice of the DBA","author_url":"http:\/\/www.voiceofthedba.com","html":"