Slashdot Mirror


There Is No Reason At All To Use MySQL: MariaDB, MySQL Founder Michael Widenius

sfcrazy writes "In this exclusive interview MySQL founder Michael Widenius talks about the reasons of decline of MySQL, what Oracle is doing wrong and how MariaDB is fast replacing it. There are quite some interesting information in this interview. The take out of this interview is '...there is no reason at all to use MySQL 5.5 instead of MariaDB 5.5. The same will be true for the next generation.'" Of course, he has an economic interest in getting people to use MariaDB. Hard to argue that Oracle isn't evil though.

20 of 241 comments (clear)

  1. Postgres by Anonymous+Brave+Guy · · Score: 5, Informative

    ...there is no reason at all to use MySQL 5.5 instead of MariaDB 5.5

    Or Postgres, which is better than MySQL in numerous objective/technical ways and has been for years.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    1. Re:Postgres by chris.alex.thomas · · Score: 4, Informative

      I'm confused, on my debian vps, another debian dedicated server and a further centos server, I could just apt-get the new software.

      since it's 100% compatible and most small websites are not even going to touch the potential problem areas, how would this cost a "lot of money" ?

      I could upgrade my database in the time it takes to download the packages, hardly a lot of money and even less of time.

    2. Re:Postgres by Anonymous+Brave+Guy · · Score: 4, Insightful

      In many ways, WordPress : CMS :: MySQL : Database.

      Both WordPress and MySQL are great success stories in terms of popularity and to some extent creating an ecosystem as a result. That doesn't make either of them particularly good technically. The way that WordPress was basically hard-coded to use a specific database is not any other database's fault. It's just another symptom of the questionable architectural decisions underlying it.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  2. Monty is a stooge by Anonymous Coward · · Score: 5, Interesting

    The Maria builds have not been particularly special, and its hard to take anything he says about MySQL seriously. So much doublespeak. Stop posting his rants as relevant or news. This is little more than an ad for his support/consulting org.

  3. That's funny by Anonymous Coward · · Score: 4, Insightful

    It's also what Postres fans have been saying for years. Maybe they're right about other things?

  4. or sqlite by mattdm · · Score: 5, Insightful

    As a general rule of thumb, if you need something lightweight, SQLite is the way to go. If you need something more powerful or sophisticated than that, PostgreSQL.

    MySQL and spinoffs all occupy an uncomfortable middle ground. 99% of the small web sites which are built around MySQL don't need it.

    1. Re:or sqlite by wmac1 · · Score: 4, Insightful

      Most people and websites do not agree with you. Ask facebook , wikipedia and thousands of others (if not millions).

      SQLite is not scalable. MySQL is lightweight and scalable.

      PostgreSQL has not been successful in penetrating cheap shared hosting providers. There is no web based tool comparable to phpMyAdmin and there are more reasons why PostgreSQL has not been successful despite its technical advantages.

    2. Re:or sqlite by gagol · · Score: 4, Funny

      The command sucks. I uses a led and a switch connected to my fiber to send commands.

      --
      Tomorrow is another day...
    3. Re:or sqlite by S.O.B. · · Score: 4, Informative

      PostgreSQL has not been successful in penetrating cheap shared hosting providers. There is no web based tool comparable to phpMyAdmin and there are more reasons why PostgreSQL has not been successful despite its technical advantages.

      Ask and ye shall receive:

      http://phppgadmin.sourceforge.net/

      --
      Some of what I say is fact, some is conjecture, the rest I'm just blowing out my ass...you guess.
    4. Re:or sqlite by shutdown+-p+now · · Score: 4, Interesting

      Firebird is trivially embedded with almost zero configuration requirements, yet scales up well and is pretty feature rich. It's a very good option when you think Postgres is overkill.

    5. Re:or sqlite by StandardDeviant · · Score: 4, Informative

      The default configs for postgres are set for a fairly small memory usage profile (*), which is fine if that's what you need (e.g. tiny vm or something that makes it a huge production to raise things like max shm size), but if you have sufficient ram, you can crank a hell of a lot more performance out of the engine by making the configs less conservative. This page is a good start: http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server

      Not that it's a priori *wrong* to run with the defaults, it'll still work just fine, but once you start having significant traffic or complicated queries you'll be happier if it more fully uses the system resources available.

      (*) It's been a good while since I last had to take a pg instance from stock and tune it, but I very vaguely recall the default settings were on the order of a eight megabytes of ram usage.

    6. Re: or sqlite by RyuuzakiTetsuya · · Score: 5, Funny

      Hey, that's not a REAL no true Scotsman fallacy...

      --
      Non impediti ratione cogitationus.
  5. Sign of OSS maturity by Gothmolly · · Score: 5, Interesting

    Most MySQL/MariaDB users wont care at all about this, because there are millions of them who are not Slashdot or Amazon or Facebook - this DB silently powers millions of Internet connected things, and it's just a given that it works, performs, has fit-for-purpose stability. It's a sign of how far OSS has come when people have the luxury of quibbling over WHICH free, capable DB they want to base their business model on.

    --
    I want to delete my account but Slashdot doesn't allow it.
  6. There Is No Reason At All To Use MySQL.. by JoeCommodore · · Score: 4, Informative

    My reason is because there is no compelling reason right now for me to switch. Once it is in my next Ubuntu upgrade or my ISP switches to it then I'll do so as well.

    --
    "Enjoy what you're doing! If it becomes drudgery, you're doing it wrong!" - Jim Butterfield
  7. Re:First by wmac1 · · Score: 4, Interesting

    Michael Widenius has benefited from gathering millions of developers around his product and letting them down.

    He cannot sell source code of MariaDB this time, but he still can sell the brand name and the community which has trusted him again to earn another fortune. Fool me once, full me twice...

  8. Postgres has a poor toolset by mveloso · · Score: 4, Interesting

    The main reason to stay away from PostgreSQL is its toolset. Specifically, it's almost impossible to find a tool that allows you to analyze and tune it's performance. I say 'almost' because there may be one out there that I haven't found...but I've looked on and off for years, with no results.

    For mysql there's lots of tools, like jetprofiler. For oracle you can pay. For SQLite, well, who cares. For psql, it's (as one website put it) a black art. Do you really want that as your back end?

    1. Re:Postgres has a poor toolset by ducomputergeek · · Score: 4, Informative

      Have you not looked at the enterprise DB folks? A few years ago I was working on a project that started out using MySQL because MySQL was everywhere and initially it was for a single store. Then that became 50 and then 200 and we ran into some interesting problems with MySQL. Long story short, we ported the backend to PostgreSQL in a couple weeks and then ran for another three years processing tens of thousands of transactions a day without further hiccups from the database before we sold the company. The plan originally was to use PostgreSQL and then migrate to DB2 at some point once the revenue was coming in. Even when we reach that point PostgreSQL was handling everything we threw at it and we did hire Enterprise DB to come in and tune the database set up since we didn't have and couldn't afford to hire a DBA full-time at that point. IIRC they had a pretty decent toolset that we used there after, but it wasn't free as in beer or speech.

      --
      "The problem with socialism is eventually you run out of other people's money" - Thatcher.
    2. Re:Postgres has a poor toolset by greg1104 · · Score: 4, Informative

      The performance analysis tools for PostgreSQL are still rough, but they're coming out stronger now than ever before. The old slow query profiling approach is based on database log files, and the pgbadger tool has gotten a lot of improvements in the last year to take the lead in that area. Some web app providers have added PostgreSQL data collection and visualization to the products recently, Datadog is a good example, they even run Postgres internally.

      Last year's PostgreSQL 9.2 added a built-in query profiling feature via an improved pg_stat_statements module. That makes it relatively easy to see what queries are taking up time on the server, in a way that matches similar statements based on underlying their query plan. I wrote a sort of call to arms to suggest how the next generation of analysis tools can leverage that in Beyond Query Logging.

      You are correct that no one has really grabbed ahold of this area and put together a really easy to use tool set around it. All of the hard to construct pieces needed are in place now, and my list of goals for this year's 9.3 development includes pushing the tuning methodology outlined in my High Performance PostgreSQL 9.0 book into some reference tool implementations. The idea that this is a "black art" is coming from consultants who want you to be intimidated. People who want to understand how things work can read my book, and then wander out to confidently build terabyte size databases. I talk with new people who have done just that every week now.

  9. Yada Yada Yada.. More of the same drivel. by FlyingGuy · · Score: 5, Insightful

    98% of "web Programmers" wouldn't know a good database if it dragged them out of the parents basement and gave them a blow job.

    I would not recommend using Oracle to run a simple web site. It is complete over kill. I would not recommend using MySQL / Maria to run the VISA processing center either.

    99.9% of application builders do not even know the value of a good, much less great, DB engine and that is proven out time and time again when you look at their DB schema and all you see are tables. They all insist on doing EVERYTHING on the front end and never get , even when advised about, the amount of power that DB's like Oracle, PostGres, MS-SQL, DB2 and even MySQL have these days. One well written Stored Procedure ( Oracle Speak ). Package ( Oracle Speak ), function ( PostGres Speak ) or Procedure ( MySQL/ MS-SQL Speak ) can eliminate 1000's of lines of java, python, ruby, php ( pick your language ) front end code, and perform the function 1000x faster and more reliably.

    Every tool has its use. When you need massive scaleibility, up time in the 5 9's category and support RIGHT FUCKING NOW WITH AN ACTUAL ENGINEER when you dial the toll free number 24/7/365 you get the big dogs like Oracle,MS-SQL or DB2. If those factors are less important then you have other choices like Postgres ( they REALLY need to fix the TXID issue ) which is very powerful but lacks the kind of SLA's that you can get with Oracle / Microsoft. If just getting feedback from the support community is fine the MySQL / Maria are fine choices.

    I design VERY large databases that push DB's to their limits. Google had to design their own because nothing off the shelf or even from the FOOS community could handle their requirements but it takes a small army to deal with it and most companies don't have the resources or don't want to have that many people on their payroll.

    The bottom line is use the DB that fits your requirements, fits your budget and has the support organization around it so when you have a problem your requirements are met, and it really does not matter who you get it from. Don't be religious about it. ALL of these companies are trying to build the best product to serve their market and that is the bottom line.

    Michael Widenius is nothing but a little bitch. He sold his DB to sun for how much again? 1 BILLION dollars I think it was. Now shut the fuck up, go sit on your riches and do MariaDB if you want but stop bitching about what happened to MySQL because he YOU are the idiot who cashed in and sold out.

    --
    Hey KID! Yeah you, get the fuck off my lawn!
  10. Re:First by Anonymous Coward · · Score: 5, Funny

    Fool me once, full me twice...

    ...empty me the third time?