• xmunk@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        4 months ago

        JSON in the DB isn’t an antipattern. It is frequently used in absolutely terrible designs but it is not itself a bad thing.

        I’m a data architect and I approve this message.

        • lengau@midwest.social
          link
          fedilink
          arrow-up
          0
          ·
          4 months ago

          Carrying the body of a smaller plane in a larger plane isn’t an antipattern either. Airbus does this between body assembly and attaching the wings.

            • Enoril@jlai.lu
              link
              fedilink
              arrow-up
              0
              ·
              4 months ago

              It’s “fuselage”.

              It’s called like that because of it came from the word “forme fuselé” (Tapered shape) and it’s a french word mainly because we created it in 1908.

              You’re welcome :-)

        • meliaesc@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          4 months ago

          Why not use nosql if your important data is stored in JSON? You can still do all your fancy little joins and whatnot.

            • xmunk@sh.itjust.works
              link
              fedilink
              arrow-up
              0
              ·
              4 months ago

              Specifically so you get mature transactional guarantees, indices and constraints that let app developers trust your db.