Conversation

Notices

  1. adiwan adiwan

    They think: "Why don't we store everything flat, use compound foreign keys, and make relations as cumbersome to find out and create views that are less helpful as they do rarely use JOIN and use a BAZILLION of WHERE clauses. WHO NEEDS READABILITY AND PERFORMANCE?

    Friday, 09-Sep-22 10:40:06 UTC from web
    1. Anna Wright Anna Wright

      @adiwan JOINS are inexpensive, but when you need do trillions of them, they become an obstacle. This problem was why Amazon created DynamoDB

      Friday, 09-Sep-22 23:19:50 UTC from web
      1. adiwan adiwan

        @oracle Well... It's not an environment with a ton of activity. A lot but not Amazon-a-lot. The database is an older Oracle installation because legacy software running needs exactly that old version. It stems from a time where entity frameworks were the rage and thus all objects were stored in a database. That same database is misused as a semi-persistent storage for message queues. In the recent past it was a few times as the culprit for some major downtime, as it is the biggest single point of failure without redundancy. I'm pretty soured by that.

        Saturday, 10-Sep-22 07:32:45 UTC from web