If you care about supporting open source software, and still use MySQL in 2026, you should switch to MariaDB like so many others have already done.\n
    • lechekaflan@lemmy.worldEnglish
      0·
      12 days ago

      Older people about to return to programming, and most of the online tutorials they have are about 20 years old, having no idea an alternative exists.

  • MrSoup@lemmy.zipEnglish
    0·
    13 days ago

    MariaDB >>>

    I’ve been using it since ever on my rpi because they say it’s easier on resources

    • YurkshireLad@lemmy.caEnglish
      0·
      13 days ago

      Who are “they”?

      We use MariaDB at work but I don’t know why it was originally chosen over PostgreSQL, as that was before my time.

      • MrSoup@lemmy.zipEnglish
        0·
        12 days ago

        Blogs and forums back then when I looked it up.
        Can’t remember exactly where (since it’s been a long time ago), but I’m sure more than someone claimed it.

  • dan@upvote.auEnglish
    0·
    13 days ago

    MariaDB is not always a drop-in replacement. There’s several features that MySQL has that MariaDB doesn’t, especially related to the optimizer (for some types of queries, MySQL will give you a more optimized execution plan compared to MariaDB). It’s also missing some newer data types, like JSON (which indexes the individual fields in JSON objects to make filtering on them more efficient).

    MariaDB and MySQL are both fine. Even though MySQL doesn’t receive as much development any more, it doesn’t really need it. It works fine. If you want a better database system, switch to PostgreSQL, not MariaDB.

        • FackCurs@lemmy.worldEnglish
          0·
          13 days ago

          Oh no… it was the easy solution for Wordpress and other plug and play self hosted services .

        • alibloke@feddit.ukEnglish
          0·
          12 days ago

          The corporation was bought by k1 capital. The foundation and therefore the open source version will always be free

        • dan@upvote.auEnglish
          0·
          13 days ago

          SQLite is underrated. I’ve used it for high traffic systems with no issues. If your system has a large number of readers and a small number of writers, it performs very well. It’s not as good for high-concurrency write-heavy use cases, but that’s not common (most apps read far more than they write).

          My use case was a DB that was created during the build process, then read on every page load.

            • dan@upvote.auEnglish
              0·
              13 days ago

              One of SQLite’s recommended use cases is as an alternate to proprietary binary formats: https://sqlite.org/appfileformat.html. Programs often store data in binary files for performance, but you get a lot of the same functionality included with SQLite (fast random access, concurrent usage, atomicity, updates that don’t need to rewrite the whole file, etc) without having to implement a file format yourself.

              I’m not sure if this is still the case, but Facebook’a HHVM used to store the compiled bytecode for the whole site in a single SQLite database: https://docs.hhvm.com/docs/hhvm/advanced-usage/repo-authoritative/. Every pageload loaded the bytecode for all required files from the DB.

              • hoppolito@mander.xyzEnglish
                0·
                12 days ago

                Fascinating read, I should definitely also make way more use of sqlite for little side projects.
                Thanks for the link!

      • msage@programming.devEnglish
        0·
        12 days ago

        Is Maria that much better than MySQL?

        Cause that one is absolute shit, very difficult to maintain, and requires lots of config changes and even replicas can disconnect when something’s not 100% ok.

        I will take Postgres over any other DB any day of the week.

    • illusionist@lemmy.zipEnglish
      0·
      13 days ago

      Depends on the task but for general usage there is no big difference. You would choose one over the other if you need one for work.

    • Rikj000@discuss.tchncs.deEnglish
      0·
      13 days ago

      Yeah,
      I did a speed test comparison between Oracle MySQL and MariaDB MySQL,
      MariaDB is about 10 times faster.

      FYI: When Oracle bought MySQL a lot of developers left and created MariaDB, so the brains behind the project moved, and in the meantime Oracle did a great job of fucking things up.

    • Roguelazer@lemmy.worldEnglish
      0·
      13 days ago

      MySQL often has moderately higher performance (particularly for workloads where you want your data clustered by PK, which is how InnoDB is natively structured) and its replication system is much more flexible than either of PostgreSQL’s. I like Percona personally, but MariaDB is fine too.

      • msage@programming.devEnglish
        0·
        12 days ago

        Is it true?

        Postgres with correct fillfactor, it doesn’t create new pages and works very fast.

        Replication in MySQL always sucked ass, only received synchronous replication in some new edition, and that also didn’t sound great.

        Postgres has logstream and logical replication, both of them can be set to various levels of synchronicity, and logical replication is configurable at least as well as MySQL is in terms of which data is sent.

    • 0_o7@lemmy.dbzer0.comEnglish
      0·
      12 days ago

      If you’re constrained by resources (CPU/RAM).

      There’s a reason most web hosts usually have mariadb and not postgres.

  • SneakyWeasel@lemmy.caEnglish
    0·
    12 days ago

    Wamp anyone? (I think thats what its called, im at work and cant check my pc) Or am i the odd one out.

  • fizzle@quokk.auEnglish
    0·
    13 days ago

    I didn’t know this was ever in question?

    Also stop calling it “my sequel”