News for hackers. Stuff that matters.
Re:Stonebraker Explains Oracle's Obsolescence, Facebook's Ch... by mrweasel on Tuesday June 02, 2015 @09:20AM (#9645608)
Isn't the fact that Facebook still manages to make MySQL work an indication that unless you doing something special, current SQL server will support most users for a very long time?

Sure Facebook might have preferred a better solution, but most of us aren't Facebook, and the solutions that would work for Facebook might not be ideal for small companies.

Re:Stonebraker Explains Oracle's Obsolescence, Facebook's Ch... by exelius on Tuesday June 02, 2015 @10:43AM (#9646160)
I think that it's more an indication that running SQL is a business requirement, not a technical one. To run your business, you need to be able to query your data in a number of ways. SQL offers the most flexibility and is essentially compatible with every reporting tool out there. Your awesome NoSQL database isn't as awesome if every software package you need to run your business requires a custom integration layer.

In other words, just because our data sets are exponentially larger doesn't mean we still don't need to be able to perform complex joins or other relational operations. The data sets are more complex, but the queries we're running on them are even more complex. While some other data stores may be optimal for niche use cases, SQL offers the best mix of speed and flexibility while still meeting the business requirements.

Re:Stonebraker Explains Oracle's Obsolescence, Facebook's Ch... by techdragon on Tuesday June 02, 2015 @09:56AM (#9645838)
No, because both PostgreSQL and MySQL both make excellent key value stores and as a consequence Facebook are sticking with the data storage tools they are used to.
Re:Stonebraker Explains Oracle's Obsolescence, Facebook's Ch... by vgt on Tuesday June 02, 2015 @09:56AM (#9645833)
I think the point of the article is that Facebook is making MySQL work, and that's exceptional. Facebook understands that they would rather not.