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…
Learn to stop using shiny new things and love MySQL
11–20 of 64 posts
Re: Learn to stop using shiny new things and love MySQL
#12A 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 f…
We begged and begged for XML support. Many releases on, they trumpeted XML support! Huzzah! The XML had a header and one huge CDATA block of the Base64 encoded blob they usually sent.
Thanks!
Re: Learn to stop using shiny new things and love MySQL
#13I wish the same for PostgreSQL
Re: Learn to stop using shiny new things and love MySQL
#14I have a particular project. The database has well over 1 billion rows in multiple tables which need joins to generate complex reporting.
As the only tech here, there is only so much I can be working on. Before... time spent on trying to get MySQL to work, was time not well spent. I spent countless hours on IRC talking to devs on #mysql/#mariadb and was told many times, you seem to have the indexes in the right places and the query was well written, you are lucky you are getting it that fast.
Sure, if I had a huge team like Instgram (who I think sharded mysql) and Pinterest. I could assign dbas to get my MySQL infrastructure to scale and possibly fork my application to work different.
I even called Percona and Mariadb and was given pricing from $50 to $70k to work the issue. Note, that they didn't even promise to resolve it. They needed between $10 to $20k up front to check my schema and the data and then the other sum to do the work. Really, almost $100k and no concrete answer?
So I don't have a team and I didn't employ Percona/Mariadb to help solve my issue. Instead, I did something completely different. Some may even say drastic.
I need something simple, that will work with the 5x9's and is very robust. So instead, I went to Postgres. I ran to Postgres. I ran and didn't look back.
With Postgres, 80% of my issues went away. PG 9.5 has some features that ALL of my issues will go away and I may be able to have quarterly queries of 10b rows with multiple tables in under 2 seconds. Cloudflare is currently doing it and I'm trying to replicate it.
Bottom line is this. MySQL for me, was a dead end. Postgres seems to every year go from strength to strength.
Postgres isn't shiny. It's dependable, actually cares what you are putting in the database. Makes your schema simple because you can go from var(x)/int(x) to text/int and it's still fast.
I've converted about 10 other dbas who were used to MySQL and thought PG was hard, to switch over. Now, like me. They won't look back.
If you are still using MySQL. Take a look at Postgres. MySQL has lost it's shine. It's now dull.
Fingers crossed PG 9.6 comes with MPP capability. That would really blow the doors off!
Re: Learn to stop using shiny new things and love MySQL
#15I understand what you're saying but please replace MySQL with Postgres. Only one of those two is an actual consistent database.
Re: Learn to stop using shiny new things and love MySQL
#16Re: Learn to stop using shiny new things and love MySQL
#17Re: Learn to stop using shiny new things and love MySQL
#18Re: Learn to stop using shiny new things and love MySQL
#19I 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
It's quite possible this is just due to people supporting existing applications, but I dunno, I am tempted to stick with MySQL for new stuff for the next little while.
Re: Learn to stop using shiny new things and love MySQL
#20How big is the team over at pinterest managing the MySQL infrastructure? I think this is the big difference here. I have a particular project. The database has well over 1 billion rows in multiple tables which need joins to generate complex reporting. As the only tech here, there is only so much I can be working on. Before... time spent on trying to get MySQL to work, was time not well spent. I spent countless hours…
The idea of Postgres being a "shiny new toy" is... an interesting viewpoint.