Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This article has many facts wrong.

It seems that MySQL development halted entirely at Sun.

I was concerned about Oracle's motives w.r.t MySQL but I can say they have come out with major new releases that improve MySQL in substantial ways. For instance, they've greatly improved the scalability of InnoDB on large SMP machines.

On the other hand, neither Sun nor Oracle have been really wanting to win with MySQL either and I think we could have seen more and different innovation in MySQL if it had been in other hands.

The Wikipedia win is big for MariaDB because it's a show of confidence that it works in demanding applications.



Was there ever a doubt that MariaDB wouldn't work in demanding applications? It's pretty much MySQL all the way down.


"No one ever got fired for buying IBM."

As a corollary, no one wants to be the guy that suggested MongoDB before it caused an outage.


I think that only makes sense if you don't know what MariaDB is. It's a fork that attempts to maintain high compatibility, run by the founder of MySQL.

What it isn't is a different program entirely, with a different protocol, syntax, scalability, consistency and community.


You missed the point. The idea is management and investor confidence, buy-in.

Here's how it works in most companies: MySQL goes down = something seriously bad happened. MariaDB went down = that database that Ted suggested sure is a piece of shit.


Well that depends on how Ted presented it, doesn't it? If he says "Let's try this other database instead of MySQL" may turn out different than if he says "Let's try this other version of MySQL put out by MariaDB".

In the end it comes down to having data to support your position though. If MariaDB goes down, and you can't answer whether it would have happened the same in MySQL, then maybe you shouldn't be making database suggestions. If it wouldn't have happened to MySQL, well then people were right to be wary, weren't they?


There are situations where MongoDB and the like are specifically more appropriate than traditional databases, and I do not include not understanding SQL syntax. In such situations where a ratio of needed scale to the resources available is particularly high, MySQL and other traditional databases are not a real option anyway.

However, there are of course also situations where, if you try to use MongoDB as a drop in replacement for a traditional database and then are surprised about data loss in exotic situations, for example, then you weren't really doing your job in the first place if the different goals never came up in your research of solutions.


It doesn't work for my employer's application.

May be the lots and lots of SPs are too much for MariaDB, but no, it is not a 100% replacement drop in.

I have tried.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: