Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why Should You Use MySQL?

jeremymorgan.com

Post reply on HN
Print view View original

31–38 of 38 posts

Re: Why Should You Use MySQL?

#31

Post by sadmysqluser »

taligent wrote: post #22
twerquie wrote: post #2

MySQL is to Postgres today as mSQL was to MySQL in 1998; more popular yet technologically inferior. In another 15 years, we will be having the same arguments about PostgreSQL and the thing that comes to replace it, whatever that may be. MySQL is in production and we have to live with it. The defences in the linked article are all valid. MySQL is a very sharp tool and can be used effectively. But its time has passed.…

Your analogy and your point is misguided. In another 15 years. MySQL will be legacy and PostgreSQL will be a footnote in history. Because what you fail to understand is that people aren't switching from SQL to SQL they are switching to NoSQL and doing so en masse. Have you not seen the huge array of NoSQL options that weren't available 15 years ago e.g. MongoDB, CouchBase, Riak, Cassandra, HBase, Redis. And the upcom…

You're mistaken if you think MySQL and PostgreSQL and the other databases are simply going to stand still during that time and you're also mistaken if you think applications which work with the SQL model will be abandoned before a better model is found.

My prediction is that every SQL and NoSQL system you mention will evolve towards being producers and consumers of SQL and NoSQL interfaces. I.e. like SQLite4 over KV, or Oracle memcache over InnoDB.

Re: Why Should You Use MySQL?

#32

Post by calinet6 »

sadmysqluser wrote: post #9

Personally I prefer PostGreSQL over MySQL for a drop in replacement on Linux based systems. It’s far superior in many ways, and something you should consider if you’re able to. Personally if I were to start a new business or had a Linux based environment and was in the planning phase I would choose PostGreSQL from the start. But it’s not always the best option for most people. What a crappy defense. There is little I…

In other words, the reason to use it is if you're already using it.

Re: Why Should You Use MySQL?

#33

Post by berlinbrown »

taligent wrote: post #27
berlinbrown wrote: post #6

Earlier quoted context omitted.

A lot of people use it. It is the Java of databases. Ironically, Oracle also is connected to Java.

> It is the Java of databases. That makes absolutely no sense what so ever. Java is the dominate enterprise development platform. MySQL is most popular in non-enteprise environments.

Calm down, it is a harmless folksy anecdotal comment on two technologies (ironically trademarked by the same company).

Java is a technology (including web plugins) that has received a lot of criticism from the community. Just recently the Department of Homeland Security had to chime in and recommend that users disable Java due to security concerns. MySQL has always received criticism due to various issues.

Re: Why Should You Use MySQL?

#34

Post by calinet6 »

taligent wrote: post #22
twerquie wrote: post #2

MySQL is to Postgres today as mSQL was to MySQL in 1998; more popular yet technologically inferior. In another 15 years, we will be having the same arguments about PostgreSQL and the thing that comes to replace it, whatever that may be. MySQL is in production and we have to live with it. The defences in the linked article are all valid. MySQL is a very sharp tool and can be used effectively. But its time has passed.…

Your analogy and your point is misguided. In another 15 years. MySQL will be legacy and PostgreSQL will be a footnote in history. Because what you fail to understand is that people aren't switching from SQL to SQL they are switching to NoSQL and doing so en masse. Have you not seen the huge array of NoSQL options that weren't available 15 years ago e.g. MongoDB, CouchBase, Riak, Cassandra, HBase, Redis. And the upcom…

Data doesn't magically become non-relational with time.

Re: Why Should You Use MySQL?

#35

Post by twerquie »

taligent wrote: post #22
twerquie wrote: post #2

MySQL is to Postgres today as mSQL was to MySQL in 1998; more popular yet technologically inferior. In another 15 years, we will be having the same arguments about PostgreSQL and the thing that comes to replace it, whatever that may be. MySQL is in production and we have to live with it. The defences in the linked article are all valid. MySQL is a very sharp tool and can be used effectively. But its time has passed.…

Your analogy and your point is misguided. In another 15 years. MySQL will be legacy and PostgreSQL will be a footnote in history. Because what you fail to understand is that people aren't switching from SQL to SQL they are switching to NoSQL and doing so en masse. Have you not seen the huge array of NoSQL options that weren't available 15 years ago e.g. MongoDB, CouchBase, Riak, Cassandra, HBase, Redis. And the upcom…

Trends are trends. ACID-compliant databases will always have their place.

Re: Why Should You Use MySQL?

#36

Post by [deleted] »

taligent wrote: post #17
yummyfajitas wrote: post #3

1 reason to use MySQL rather than Postgres: 1) Your legacy shared hosting site might provide MySQL and not Postgres. There are also 9 reasons to choose one of {Postgres, MySQL} over {Oracle, SQL Server}. Here is 1 reason to use Postgres: data integrity. "00/00/0000 00:00:00.0000" is not a real date, but MySQL will helpfully insert it into your table if you try to insert NULL into a non-null datetime field. (One examp…

2) Clustering e.g. multi-master solution. 3) Decent monitoring. 4) Commercial support. And your argument about data integrity is valid but in the real world moot. Most developers are using an ORM these days which abstract problems like these away.

[deleted]

Re: Why Should You Use MySQL?

#37

Post by toddh »

AaronBBrown wrote: post #14
toddh wrote: post #7

RDS as a scaling strategy is also a good reason.

RDS isn't really that great as a scaling strategy. It's only marginally easier to keep running than your own dedicated MySQL instances and it's far less flexible, particularly for disaster recovery since there is no way to do cross-region replication.

Marginally for who and it what scenarios? Features like Provisioned IOPS and Multi-AZ deployment with failover and read replicas make it quite attractive for a project without a lot of dedicated staff. So it's great strategy depending on what you want to do.

Re: Why Should You Use MySQL?

#38

Post by EugeneOZ »

taligent wrote: post #17
yummyfajitas wrote: post #3

1 reason to use MySQL rather than Postgres: 1) Your legacy shared hosting site might provide MySQL and not Postgres. There are also 9 reasons to choose one of {Postgres, MySQL} over {Oracle, SQL Server}. Here is 1 reason to use Postgres: data integrity. "00/00/0000 00:00:00.0000" is not a real date, but MySQL will helpfully insert it into your table if you try to insert NULL into a non-null datetime field. (One examp…

2) Clustering e.g. multi-master solution. 3) Decent monitoring. 4) Commercial support. And your argument about data integrity is valid but in the real world moot. Most developers are using an ORM these days which abstract problems like these away.

multi-master in MySQL?
Post reply on HN