Results 1 to 10 of 10

Thread: Facebook & Others Announce WebScaleSQL

  1. #1
    Join Date
    Jan 2007
    Posts
    15,080

    Default Facebook & Others Announce WebScaleSQL

    Phoronix: Facebook & Others Announce WebScaleSQL

    A number of tech companies including Facebook, Google, LinkedIn, and Twitter announced WebScaleSQL on Thursday as a project that adapts MySQL to their massively bigger database needs...

    http://www.phoronix.com/vr.php?view=MTY0NjA

  2. #2
    Join Date
    Apr 2011
    Location
    Atlanta, GA, USA
    Posts
    12

    Default MariaDB

    Does anyone have any ideas why they forked MySQL instead of working with the MariaDB community?

  3. #3
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,909

    Default

    Quote Originally Posted by ImNtReal View Post
    Does anyone have any ideas why they forked MySQL instead of working with the MariaDB community?
    I was wondering the same thing. Its a fork anyway, may as well fork the better product

  4. #4

    Default

    Quote Originally Posted by Ericg View Post
    I was wondering the same thing. Its a fork anyway, may as well fork the better product
    All these guys deployed MySQL for a very long time before any such forks existed and moving to a fork is very much a intrusive and expensive change even if the fork is mostly compatible.

  5. #5
    Join Date
    Nov 2013
    Posts
    45

    Default

    Quote Originally Posted by ImNtReal View Post
    Does anyone have any ideas why they forked MySQL instead of working with the MariaDB community?
    From their FAQ:
    Q: Why didn't you base this on MariaDB, Percona Server, Drizzle, etc....
    A: We reached a consensus that MySQL-5.6 was the right choice for this, as it has the production-ready features we need to operate at scale, and the features planned for MySQL-5.7 seem like a fitting path forward for us. We will continue to revisit this decision as the ecosystem evolves.

  6. #6
    Join Date
    Nov 2010
    Posts
    74

    Default

    I checked some changes in the repo - it's not very impresive in term of features - because this fork is about performance. I hope that MariaDB developers will pick all of sensible changes from this fork and port them to Maria 10.

  7. #7
    Join Date
    Nov 2013
    Posts
    45

    Default

    Quote Originally Posted by michal View Post
    I checked some changes in the repo - it's not very impresive in term of features - because this fork is about performance. I hope that MariaDB developers will pick all of sensible changes from this fork and port them to Maria 10.
    Or rather, create a branch which is similar to this, and not mainline it into MariaDB, the reason is similar to why they don't just mainline their changes into MySQL.

  8. #8
    Join Date
    Feb 2013
    Posts
    275

    Default

    Quote Originally Posted by RahulSundaram View Post
    All these guys deployed MySQL for a very long time before any such forks existed and moving to a fork is very much a intrusive and expensive change even if the fork is mostly compatible.
    I don't know about the other companies, but in the case of Google, I was under the impression that Google migrated all of the data that was in MySQL to MariaDB last year. However, I would expect that the Google devs who worked on WebScaleSQL and the Google sysadmins responsible for Google's MariaDB deployments probably don't talk to each other and don't have any bosses in common.

  9. #9
    Join Date
    Nov 2013
    Posts
    45

    Default

    Quote Originally Posted by Serge View Post
    I don't know about the other companies, but in the case of Google, I was under the impression that Google migrated all of the data that was in MySQL to MariaDB last year. However, I would expect that the Google devs who worked on WebScaleSQL and the Google sysadmins responsible for Google's MariaDB deployments probably don't talk to each other and don't have any bosses in common.
    But even so they should know that they are using MariaDB. Maybe they think it is worthy enough to migrate to WebScaleSQL, since this may reduce their server loads and increase service efficiency quite a bit. In the long term, IMHO WebScaleSQL is indeed the better choice, they might not have expected this to come and therefore MariaDB might have been a bad decision considering that they will soon change their database system once again (or perhaps the MariaDB has paid off already during its short usage term).

    Or probably this is all wrong, maybe they are only using this for new services? Or they might even make WebScaleSQL and MariaDB interoperable?
    IDK, I'm not an expert in databases perhaps I can learn quite a few things from here

  10. #10
    Join Date
    Aug 2010
    Posts
    31

    Default

    I don't know if Google internally use MariaDB, but YouTube does use MySQL in a non-traditional way:

    http://www.youtube.com/watch?v=qATTTSg6zXk

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •