• Simulation6@sopuli.xyz
    1·
    4 hours ago

    The DoD funded a lot of the early development of relational databases, along with internet protocol. Working for the cia was probably the least of ellisons sins. Really bad company, but solid DB.

    • 🍉 Albert 🍉@lemmy.world
      1·
      18 minutes ago

      y’all wrong, the worst database in existence is wherever I keep my notes. because every time I write notes I forget where the fuck I wrote them.

    • locuester@lemmy.zipEnglish
      62·
      20 hours ago

      Based on what? It’s top notch for immutability, zero trust, proof of existence, accountability, transparency, uptime, decentralization, network resilience…

      • chaospatterns@lemmy.worldEnglish
        5·
        3 hours ago

        What about throughput, latency, schema modeling, query load balancing/routing, confidentiality, regulatory compliance, operational tooling? How easily can I write a CRUD or line of business service using it?

        • locuester@lemmy.zipEnglish
          1·
          1 hour ago

          Confidentiality, regulatory compliance, schema modeling (IDLs?), query load balancing (rpc infra) and operational tooling pretty good in my world now (Solana). Throughout and latency decent now (400ms conf, couple second finality, 4k tps) but obviously the type of system that needs a trustless immutable database has tradeoffs.

          How easily can you write a crud system? No clue that’s on you. A line of business service? Why the hell would that need a trustless immutable ledger. You’re barking up the wrong tree. Low level financial systems are pretty much the only thing that benefits. Small niche for proof of existence perhaps. And maybe other immutable use case things.

      • Rooster326@programming.dev
        101·
        13 hours ago

        A400 is at least relational.

        MongoDB on the other hand…

        All data is, or will become, relational.

        • LeFantome@programming.dev
          11·
          6 hours ago

          I am a big SQL fan but not all data has to be relational.

          Let’s say I want the GPS coordinates of ten million vehicles every 5 seconds. I have a vehicle id, a timestamp, and coordinates. I do not care if a few writes get lost. Why does this have to be relational?

          And perhaps I also record other info that may change from vehicle to vehicle. Perhaps just values that are true if present. DoorOpen, BrakeApplied, LightsOn, LightBarOn, EngineOn, etc. I may only be displaying this data in a UI. I may get different values from every vehicle or even every write. There is no “schema”. I mean, I can have a JSON field or something in my relational table? But this is not exactly relational anymore.

          • Rooster326@programming.dev
            21·
            5 hours ago

            Correct not all data has to be relational but it will always eventually become relational. You will at one point want to pair that vehicle id to a vehicle and then again to something else.

  • drolex@sopuli.xyz
    68·
    2 days ago

    Hahaha this is cartoonishly evil, surely it can’t be true!

    Next you’ll tell me Ellison invests in creepy life extension projects and gives an insane amount of money to post-fascist politicians!

  • bss03@infosec.pubEnglish
    241·
    2 days ago

    Oracle is not the worse DB in existence. They are a worse company than MS, but I’d much rather be talking to Oracle than MSSQL.

    (My go-to is PostgreSQL, tho.)

  • xcaliber47@europe.pub
    4·
    2 days ago

    Hate to be the Devils advocate here, but Oracle is the only one (as far as i know) which provides a FREE usable server. FOREVER. Via OracleCloud