5 ms·

I'm researching migrating from Sybase to MySQL and this looks like an interesting alternative considering MariaDB is released under GNU GPL and is a fork of MyS

by j-b 13y ago

I'm researching migrating from Sybase to MySQL and this looks like an interesting alternative considering MariaDB is released under GNU GPL and is a fork of MySQL outside of Oracle control. Are there any weak points in MariaDB worth noting?

atmosx 13y ago
I used MySQL for all my projects. However I'm following the tide and moving to PSQL. Apparently it is more flexible and has more options to tinker with.
mrmondo 13y ago
Have a read of this: http://grimoire.ca/mysql/choose-something-else http://grimoire.ca/mysql/choose-something-else
- jakejake 13y ago
  A fair portion this guy's posts seem to be criticizing people for using certain tools/techniques and how much various things suck.
  - gcv 13y ago
    Does that make him wrong?
    - rimantas 13y ago
      As much as cherry-picking makes anyone wrong. Replication is one of the main reasons some big project choose MySQL and the guy ignores that point and only mentions replication in passing. I am sure you can have as good a selection of reasons to avoid PostgreSQL or any other. That does not really matter though. Some guy who never bothered to read MySQL documentation is now switching to PGSQL and will run it without bothering to read any documentation. It does not matter because his project is so trivial it would run on anything, but he is happy because he uses "the real database". So be it. And the guys who really do know what's going on and run systems with hundreds of millions of users don't waste their time writing bullshit articles like this. Guy recomends MongoDB as an alternative, what can I say.
      - julie1 13y ago
        replication in mysql? Well, kind of random, I remember @work people not getting it right for 3 years... because they forgot to read the documentation. We may have too much clueless developer in the wild, imitating for security. Like the more linux is spreading, the more the sect of the post devil spread, you recognize them with their dark incatation: chmod 777 (the number of the post devil) and chown root:root.
      - sergiosgc 13y ago
        I see this explanation a lot. However, from what I can gather: - pgsql supports synchronous master-slave replication natively, with excellent performance - mysql supposedly does multi-master replication, but does not solve the hard problems. You can't write on the same row on two masters simultaneously or replication stops; sequential ids are not synchronized between masters; you can't get serial transaction isolation between masters. All in all, I'd rate replication support between both databases as nearly identical. Pgsql does master-slave better, mysql has a half-hearted attempt at multi master. Given that on all else pgsql is markedly better, I can't see replication as the reason for picking mysql.
      - epo 13y ago
        What use is replication if the data itself has been mangled by MySQL? The significant arguments against MySQL revolve around it doing a poor job of enforcing data integrity. You go on to claim he hasn't bothered to read the documentation but give no evidence other than wild fanboy accusations that you have read it either. There are plenty of assertions in that blog post, none of which you refute; from which I can conclude you have no arguemnts against what he actually said.
  - copergi 13y ago
    Lots of people build up massive amounts of technical debt by using the wrong things. Things like mysql literally hold back progress. "Stop using garbage" is an important message to spread.
    - jakejake 13y ago
      Dismissing things as garbage when they clearly are not - that's just the other side of the same coin. It can equally cloud your vision for choosing the right tool for the job.
      - copergi 13y ago
        >Dismissing things as garbage when they clearly are not That is not the case here. Did you read the site?
        jakejake 13y ago
        I read the site but I didn't drink the kool-aid!
mmsimanga 13y ago
By all means read all the good and bad articles about MySQL/MariaDB. Just keep in mind that the presence of detrators of a technology is not a sign the technology should not be used. Just think of all those articles proclaiming Java is dead.
pvg 13y ago
Weakest (or strongest, depending on your goals and tastes) are comparative newness and divergence from MySQL 5.6. This is a nice short summary from the Percona dude: http://www.percona.com/resources/technical-presentations/meet-mariadb-100-percona-university-washington-dc-2013 http://www.percona.com/resources/technical-presentations/mee...
stephen_g 13y ago
Have you considered PostgreSQL? MariaDB would probably be fine and has the advantage of having a lot more tutorials on the internet (makes it a tiny bit easier to get started), but Postgres is the best open source database there is (in my opinion at least). I don't bother with MySQL/MariaDB for my own projects anymore (I started on it 10 years ago). I only ever use it if I'm installing something that won't work with anything else.
ams6110 13y ago
Why do you want to migrate away from Sybase? You'd be giving up a lot of capabilities moving to Maria/MySQL. Given the common ancestry, your easiest transition would be to SQL Server. But if your reasons are to get out from under from vendor control, that isn't really achieving anything.
- j-b 13y ago
  Hedging bets against license cost inflation due to the recent SAP acquisition.

by j-b 13y ago

atmosx 13y ago

I used MySQL for all my projects. However I'm following the tide and moving to PSQL. Apparently it is more flexible and has more options to tinker with.

mrmondo 13y ago

Have a read of this: http://grimoire.ca/mysql/choose-something-else http://grimoire.ca/mysql/choose-something-else

jakejake 13y ago
A fair portion this guy's posts seem to be criticizing people for using certain tools/techniques and how much various things suck.
- gcv 13y ago
  Does that make him wrong?
  - rimantas 13y ago
    As much as cherry-picking makes anyone wrong. Replication is one of the main reasons some big project choose MySQL and the guy ignores that point and only mentions replication in passing. I am sure you can have as good a selection of reasons to avoid PostgreSQL or any other. That does not really matter though. Some guy who never bothered to read MySQL documentation is now switching to PGSQL and will run it without bothering to read any documentation. It does not matter because his project is so trivial it would run on anything, but he is happy because he uses "the real database". So be it. And the guys who really do know what's going on and run systems with hundreds of millions of users don't waste their time writing bullshit articles like this. Guy recomends MongoDB as an alternative, what can I say.
    - julie1 13y ago
      replication in mysql? Well, kind of random, I remember @work people not getting it right for 3 years... because they forgot to read the documentation. We may have too much clueless developer in the wild, imitating for security. Like the more linux is spreading, the more the sect of the post devil spread, you recognize them with their dark incatation: chmod 777 (the number of the post devil) and chown root:root.
    - sergiosgc 13y ago
      I see this explanation a lot. However, from what I can gather: - pgsql supports synchronous master-slave replication natively, with excellent performance - mysql supposedly does multi-master replication, but does not solve the hard problems. You can't write on the same row on two masters simultaneously or replication stops; sequential ids are not synchronized between masters; you can't get serial transaction isolation between masters. All in all, I'd rate replication support between both databases as nearly identical. Pgsql does master-slave better, mysql has a half-hearted attempt at multi master. Given that on all else pgsql is markedly better, I can't see replication as the reason for picking mysql.
    - epo 13y ago
      What use is replication if the data itself has been mangled by MySQL? The significant arguments against MySQL revolve around it doing a poor job of enforcing data integrity. You go on to claim he hasn't bothered to read the documentation but give no evidence other than wild fanboy accusations that you have read it either. There are plenty of assertions in that blog post, none of which you refute; from which I can conclude you have no arguemnts against what he actually said.
- copergi 13y ago
  Lots of people build up massive amounts of technical debt by using the wrong things. Things like mysql literally hold back progress. "Stop using garbage" is an important message to spread.
  - jakejake 13y ago
    Dismissing things as garbage when they clearly are not - that's just the other side of the same coin. It can equally cloud your vision for choosing the right tool for the job.
    - copergi 13y ago
      >Dismissing things as garbage when they clearly are not That is not the case here. Did you read the site?
      - jakejake 13y ago
        I read the site but I didn't drink the kool-aid!

mmsimanga 13y ago

By all means read all the good and bad articles about MySQL/MariaDB. Just keep in mind that the presence of detrators of a technology is not a sign the technology should not be used. Just think of all those articles proclaiming Java is dead.

pvg 13y ago

Weakest (or strongest, depending on your goals and tastes) are comparative newness and divergence from MySQL 5.6. This is a nice short summary from the Percona dude: http://www.percona.com/resources/technical-presentations/meet-mariadb-100-percona-university-washington-dc-2013 http://www.percona.com/resources/technical-presentations/mee...

stephen_g 13y ago

Have you considered PostgreSQL? MariaDB would probably be fine and has the advantage of having a lot more tutorials on the internet (makes it a tiny bit easier to get started), but Postgres is the best open source database there is (in my opinion at least). I don't bother with MySQL/MariaDB for my own projects anymore (I started on it 10 years ago). I only ever use it if I'm installing something that won't work with anything else.

ams6110 13y ago

Why do you want to migrate away from Sybase? You'd be giving up a lot of capabilities moving to Maria/MySQL. Given the common ancestry, your easiest transition would be to SQL Server. But if your reasons are to get out from under from vendor control, that isn't really achieving anything.

j-b 13y ago
Hedging bets against license cost inflation due to the recent SAP acquisition.