Hacker News new | past | comments | ask | show | jobs | submit login

It shows that a big company like Amazon, hiring thousands of SDEs still needed other vendors software than their own, because of all that time they spent in hiring and firing people and obsessing over their customers needs.

sarcasm




Also, MySQL is technically, an Oracle database (after Sun got bought out). Now they should write some migrations to turn all of that off.

sarcasm intensifies


I expect the internal teams use Amazon Aurora instead of MySQL. Aurora is compatible with MySQL but is not owned by Oracle.


Yeah but the client interfaces are all MySQL. Oracle should buy off PostgreSQL too. And then it should start charging only Amazon for using these interfaces.

moar sarcasm.



There was also MaxDB, and a few other that Monty built. There's also Percona, WebscaleSQL and a few other forks.

Amazon have been using MySQL even before all these forks happened. And not only that, if Oracle decided to pursue a lawsuit, or if MariaDB, Percona, Elasticsearch or EnterpriseDB did, Amazon will have to cough up.

This is not really a thing that Amazon should be bragging about, because it makes no real sense! They still run a lot of software they did not write.


Note: Amazon employee, but opinions are mine.

Amazon did not replace Oracle with MySQL. You seems to talk a lot given your knowledge of how Amazon operates internally and how licensing works is... blatantly false.

All of those DB's that could "pursue" a lawsuit are built on open source licenses which Amazon is not violating.

But the most important point here: The idea that you have to write a database to be happy to be off Oracle is insane. Amazon moved to an alternative that doesn't have a deep license designed to financially screw their clients as much as possible. That's a win.


1. When did I say that Amazon replaced Oracle with MySQL? I just said that MySQL is an Oracle database.

2. Open Source licenses that Amazon is not violating - a 3rdparty lawyer would be able to ascertain better about the extent of legality on Amazon's changes and its contribution back to open source software than you and I do.

3. Ex-Amazon employee here. My comments are purely based on my observation - and purely my opinions. Why can't I talk a lot?


1. I assumed it was implied. Why else bring it up?

2. If there was a means to sue Amazon for hosting databases, Oracle would have already done it a LONG time ago with MySQL. The burden is on you to prove your claim.

3. You are free to talk as much as you want, just expect push back when you aren't right, a lot. ;)


1. and 2. Amazon does use a lot of MySQL, and the fact that they still do. Oracle can determine when and how it wants to bill Amazon. You and I can't change any of that.

3. Except when the other person isn't. You just lost me on the last comment.


>Amazon have been using MySQL even before all these forks happened. And not only that, if Oracle decided to pursue a lawsuit, or if MariaDB, Percona, Elasticsearch or EnterpriseDB did, Amazon will have to cough up.

Pursue a lawsuit over... what, exactly?


No, it means that Amazon reached the point of considering other solutions than Oracle (I bet partially because of cost) at the time when this project started to move their database workloads that at the time were residing on Oracle to something else. Amazon uses many software vendors, they by no mean suffer from the NIH (not invented here) plague.




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

Search: