Slashdot Mirror

← Back to Stories (view on slashdot.org)

8 Reasons Not To Use MySQL (And 5 To Adopt It)

Posted by Zonk on from the for-every-product-turn-turn-turn dept.

Esther Schindler writes "Database decisions are never easy, even — or maybe especially — when one choice is extremely popular. To highlight the advantages and disadvantages of the open-source MySQL DBMS, CIO.com asked two open-source experts to enumerate the reasons to choose MySQL and to pick something else. Tina Gasperson takes the 5 reasons to use MySQL side, and Brent Toderash discusses 8 reasons not to. Note that this isn't an 'open source vs proprietary databases' comparison; it's about MySQL's suitability in enterprise situations."

3 of 288 comments (clear)

  1. First reason not to... by mobby_6kl · · Score: 0, Flamebait

    1) It's not a real database

  2. Ah, yes. Enterprise. by Anonymous Coward · · Score: 0, Flamebait

    I know all about enterprise solutions. Those guys over at dailyWTF?! can't shut up about them. Every developer should model himself after what Enterprise Pushers say, because they obviously know best. XML, COM+ and J2EE for teh people!

  3. Who am I Supposed to be Rooting for, Here? by hardburn · · Score: 0, Flamebait

    The MySQL supporter is raving about the large talent pool of MySQL developers, and the detractor is raving about the GPL.

    Yes, there are lots of people who have "MySQL" on their resumes, right next to "PHP". They're all clueless ninnies. If they weren't clueless ninnies, they would have chosen PostgreSQL years ago. Yes, you can hire clueless ninnies on the cheap. That's not the point.

    What does the license have to do with it? I can conceive of a project where I'm going to be bundling up a database with my application and selling it. Why would your code be so deeply integrated with the database that you legally have to sell the whole thing under the GPL?

    --
    Not a typewriter