Live data from Hacker News

Learn to stop using shiny new things and love MySQL

engineering.pinterest.com

1–10 of 64 posts

Re: Learn to stop using shiny new things and love MySQL

#4
A couple years ago I built a very robust and intricate virtual inventory system for integrating with third-party vendors. I created two accessible endpoints: one highly customizeable webservice endpoint (I'll literally take any valid XML and work with you to transform it into what I need), and one luddite-friendly SFTP server supporting extraordinarily simple export-from-excel XML output.

I was raked over the coals for providing the SFTP/Excel solution, "FTP?! What is this, the '80s?" was the quote that sticks with me.

Almost all of our vendors turned out to be small shops. Only two of our dozens of vendors use the webservice, even as easy-like-Sunday-morning as it is. Everyone else uses the Excel solution.

It's hard to let yourself write the uncool solution that actually fits the bill.

Re: Learn to stop using shiny new things and love MySQL

#5
I agree, I've found through painful experience that the shiny and new, while incredibly fun, tends to cost more than it's worth.

With that said, if you're going to take the prudent route and use an established database platform, why in the name of all that is holy would you pick MySQL over Postgres?

Granted, I am rather biased, but I do have extensive experience using both in anger. Every time I have to use MySQL I walk away with the impression that it was built with the same design mentality that PHP was. The whole point of a transactional RDBMS is to keep your data as consistent and accurate as possible. I cannot in good faith use a database that (silently!) will coerce badly formatted input into what it thinks should be in the column.

Re: Learn to stop using shiny new things and love MySQL

#7
post #5

I agree, I've found through painful experience that the shiny and new, while incredibly fun, tends to cost more than it's worth. With that said, if you're going to take the prudent route and use an established database platform, why in the name of all that is holy would you pick MySQL over Postgres? Granted, I am rather biased, but I do have extensive experience using both in anger. Every time I have to use MySQL I w…

I don't know why anyone in 2015 would pick mysql when postgres is an option. Live postgres. So nice to work with. It's json support is amazing too
Post reply on HN