Jump to content

WebScaleSQL: Difference between revisions

Edit links
From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
rmv - self-promotional namedropping and link spam
Citation bot (talk | contribs)
Bots
5,659,230 edits
Alter: title. | Use this bot. Report bugs. | Suggested by Jamesluiz102 | Category:2014 software | via #UCB_Category 49/83
Line 24: Line 24:
| url = https://github.com/webscalesql/webscalesql-5.6/commits/webscalesql-5.6.27
| url = https://github.com/webscalesql/webscalesql-5.6/commits/webscalesql-5.6.27
| title = WebScaleSQL commits history
| title = WebScaleSQL commits history
| date = {{date|2016-01-22|mdy}} | accessdate = {{date|2016-12-12|mdy}}
| date = {{date|2016-01-22|mdy}} | access-date = {{date|2016-12-12|mdy}}
}}</ref>
}}</ref>
| programming language = [[C (programming language)|C]], [[C++]], [[Perl]] and [[Bash (Unix shell)|Bash]]
| programming language = [[C (programming language)|C]], [[C++]], [[Perl]] and [[Bash (Unix shell)|Bash]]
Line 43: Line 43:
| url = http://www.zdnet.com/webscalesql-mysql-for-facebook-sized-databases-7000027814/
| url = http://www.zdnet.com/webscalesql-mysql-for-facebook-sized-databases-7000027814/
| title = WebScaleSQL: MySQL for Facebook-sized databases
| title = WebScaleSQL: MySQL for Facebook-sized databases
| date = {{date|2013-03-28|mdy}} | accessdate = {{date|2014-04-01|mdy}}
| date = {{date|2013-03-28|mdy}} | access-date = {{date|2014-04-01|mdy}}
| author = Steven J. Vaughan-Nichols | work = [[ZDNet]]
| author = Steven J. Vaughan-Nichols | work = [[ZDNet]]
}}</ref><ref>{{cite magazine
}}</ref><ref>{{cite magazine
| url = https://www.wired.com/2014/03/webscalesql/
| url = https://www.wired.com/2014/03/webscalesql/
| title = Google and Facebook Team Up to Modernize Old-School Databases
| title = Google and Facebook Team Up to Modernize Old-School Databases
| date = {{date|2013-03-27|mdy}} | accessdate = {{date|2014-04-01|mdy}}
| date = {{date|2013-03-27|mdy}} | access-date = {{date|2014-04-01|mdy}}
| author = Klint Finley | magazine = [[Wired (magazine)|Wired]]
| author = Klint Finley | magazine = [[Wired (magazine)|Wired]]
}}</ref>
}}</ref>
Line 55: Line 55:
| url = https://www.theregister.co.uk/2014/03/27/webscalesql_launch/
| url = https://www.theregister.co.uk/2014/03/27/webscalesql_launch/
| title = Forkin' 'L! Facebook, Google and friends create WebScaleSQL from MySQL&nbsp;5.6
| title = Forkin' 'L! Facebook, Google and friends create WebScaleSQL from MySQL&nbsp;5.6
| date = {{date|2013-03-27|mdy}} | accessdate = {{date|2014-04-01|mdy}}
| date = {{date|2013-03-27|mdy}} | access-date = {{date|2014-04-01|mdy}}
| author = Jack Clark | website = [[The Register]]
| author = Jack Clark | website = [[The Register]]
}}</ref><ref name="webscalesql-faq">{{Cite web
}}</ref><ref name="webscalesql-faq">{{Cite web
| url = http://webscalesql.org/faq.html
| url = http://webscalesql.org/faq.html
| title = Frequently Asked Questions
| title = Frequently Asked Questions
| date = {{date|2014-03-27|mdy}} | accessdate = {{date|2014-04-01|mdy}}
| date = {{date|2014-03-27|mdy}} | access-date = {{date|2014-04-01|mdy}}
| website = webscalesql.org
| website = webscalesql.org
}}</ref>
}}</ref>
Line 67: Line 67:
| url = http://webscalesql.org/blog/2016/12/02/Moving-Forward.html
| url = http://webscalesql.org/blog/2016/12/02/Moving-Forward.html
| title = WebScaleSQL Moving Forward
| title = WebScaleSQL Moving Forward
| date = {{date|2016-12-29|mdy}} | accessdate = {{date|2016-12-29|mdy}}
| date = {{date|2016-12-29|mdy}} | access-date = {{date|2016-12-29|mdy}}
}}</ref>
}}</ref>


Line 73: Line 73:
Running MySQL on numerous [[Server (computing)|servers]] with large amounts of data, at the scale of [[terabyte]]s and [[petabyte]]s of data, creates a set of difficulties that in many cases arise the need for implementing specific customized MySQL features, or the need for introducing functional changes to MySQL. More than a few companies have faced the same (or very similar) set of difficulties in their [[production environment]]s, which used to result in the availability of multiple solutions for similar challenges.<ref name="theregister-20140327" /><ref>{{Cite web
Running MySQL on numerous [[Server (computing)|servers]] with large amounts of data, at the scale of [[terabyte]]s and [[petabyte]]s of data, creates a set of difficulties that in many cases arise the need for implementing specific customized MySQL features, or the need for introducing functional changes to MySQL. More than a few companies have faced the same (or very similar) set of difficulties in their [[production environment]]s, which used to result in the availability of multiple solutions for similar challenges.<ref name="theregister-20140327" /><ref>{{Cite web
| url = http://code.google.com/p/google-mysql-tools/wiki/Mysql5Patches
| url = http://code.google.com/p/google-mysql-tools/wiki/Mysql5Patches
| title = Patches for MySQL&nbsp;5 – MySQL tools released by Google
| title = Patches for MySQL&nbsp;5 – MySQL tools released by Google
| date = {{date|2011-06-24|mdy}} | accessdate = {{date|2014-04-01|mdy}}
| date = {{date|2011-06-24|mdy}} | access-date = {{date|2014-04-01|mdy}}
| website = code.google.com
| website = code.google.com
}}</ref><ref>{{Cite web
}}</ref><ref>{{Cite web
| url = https://github.com/facebook/mysql-5.1
| url = https://github.com/facebook/mysql-5.1
| title = facebook/mysql-5.1
| title = facebook/mysql-5.1
| date = June 2013 | accessdate = {{date|2014-04-01|mdy}}
| date = June 2013 | access-date = {{date|2014-04-01|mdy}}
| website = github.com
| website = github.com
}}</ref>
}}</ref>
Line 86: Line 86:
| url = http://webscalesql.org/blog/2015/01/15/Welcome-Alibaba.html
| url = http://webscalesql.org/blog/2015/01/15/Welcome-Alibaba.html
| title = Please welcome Alibaba to WebScaleSQL!
| title = Please welcome Alibaba to WebScaleSQL!
| date = {{date|2015-01-15|mdy}} | accessdate = {{date|2015-08-15|mdy}}
| date = {{date|2015-01-15|mdy}} | access-date = {{date|2015-08-15|mdy}}
| website = webscalesql.org
| website = webscalesql.org
}}</ref>), aiming to provide a centralized development structure for extending MySQL with new features specific to its large-scale deployments, such as building large [[replicated database]]s running on [[server farms]]. As a result, WebScaleSQL attempted to open a path toward deduplicating the efforts each founding company had been putting into maintaining its own branch of MySQL, and toward bringing together more developers.<ref name="zdnet-7000027814" /><ref name="webscalesql-faq" /><ref name="informationweek">{{Cite web
}}</ref>), aiming to provide a centralized development structure for extending MySQL with new features specific to its large-scale deployments, such as building large [[replicated database]]s running on [[server farms]]. As a result, WebScaleSQL attempted to open a path toward deduplicating the efforts each founding company had been putting into maintaining its own branch of MySQL, and toward bringing together more developers.<ref name="zdnet-7000027814" /><ref name="webscalesql-faq" /><ref name="informationweek">{{Cite web
| url = http://www.informationweek.com/big-data/software-platforms/facebook-debuts-web-scale-variant-of-mysql-/d/d-id/1141521
| url = http://www.informationweek.com/big-data/software-platforms/facebook-debuts-web-scale-variant-of-mysql-/d/d-id/1141521
| title = Facebook Debuts Web-Scale Variant of MySQL
| title = Facebook Debuts Web-Scale Variant of MySQL
| date = {{date|2014-03-27|mdy}} | accessdate = {{date|2015-08-15|mdy}}
| date = {{date|2014-03-27|mdy}} | access-date = {{date|2015-08-15|mdy}}
| author = Doug Henschen | website = informationweek.com
| author = Doug Henschen | website = informationweek.com
}}</ref>
}}</ref>
Line 101: Line 101:
| url = http://webscalesql.org/contributing.html
| url = http://webscalesql.org/contributing.html
| title = Is Your Change Appropriate?
| title = Is Your Change Appropriate?
| date = {{date|2014-03-27|mdy}} | accessdate = {{date|2014-04-01|mdy}}
| date = {{date|2014-03-27|mdy}} | access-date = {{date|2014-04-01|mdy}}
| website = webscalesql.org
| website = webscalesql.org
}}</ref> {{As of|2014|9|15|df=US}}, available new features and changes included the following:<ref name="webscalesql-faq" /><ref name="informationweek" /><ref>{{Cite web
}}</ref> {{As of|2014|9|15|df=US}}, available new features and changes included the following:<ref name="webscalesql-faq" /><ref name="informationweek" /><ref>{{Cite web
| url = https://www.phoronix.com/scan.php?page=news_item&px=MTY0NjA
| url = https://www.phoronix.com/scan.php?page=news_item&px=MTY0NjA
| title = Facebook & Others Announce WebScaleSQL
| title = Facebook & Others Announce WebScaleSQL
| date = {{date|2014-03-28|mdy}} | accessdate = {{date|2014-04-01|mdy}}
| date = {{date|2014-03-28|mdy}} | access-date = {{date|2014-04-01|mdy}}
| author = Michael Larabel | publisher = [[Phoronix]]
| author = Michael Larabel | publisher = [[Phoronix]]
}}</ref><ref>{{Cite web
}}</ref><ref>{{Cite web
| url = https://code.facebook.com/posts/1474977139392436/webscalesql-a-collaboration-to-build-upon-the-mysql-upstream/
| url = https://code.facebook.com/posts/1474977139392436/webscalesql-a-collaboration-to-build-upon-the-mysql-upstream/
| title = WebScaleSQL: A collaboration to build upon the MySQL upstream
| title = WebScaleSQL: A collaboration to build upon the MySQL upstream
| date = {{date|2014-03-27|mdy}} | accessdate = {{date|2015-08-16|mdy}}
| date = {{date|2014-03-27|mdy}} | access-date = {{date|2015-08-16|mdy}}
| author = Steaphan Greene | website = code.facebook.com
| author = Steaphan Greene | website = code.facebook.com
}}</ref><ref>{{Cite web
}}</ref><ref>{{Cite web
| url = http://www.informationweek.com/big-data/big-data-analytics/facebook-announces-webscalesql-upgrade-for-mysql/d/d-id/1315741
| url = http://www.informationweek.com/big-data/big-data-analytics/facebook-announces-webscalesql-upgrade-for-mysql/d/d-id/1315741
| title = Facebook Announces WebScaleSQL Upgrade For MySQL
| title = Facebook Announces WebScaleSQL Upgrade For MySQL
| date = {{date|2014-09-15|mdy}} | accessdate = {{date|2015-08-16|mdy}}
| date = {{date|2014-09-15|mdy}} | access-date = {{date|2015-08-16|mdy}}
| author = Doug Henschen | website = informationweek.com
| author = Doug Henschen | website = informationweek.com
}}</ref>
}}</ref>
Line 127: Line 127:
| url = https://dev.mysql.com/doc/refman/5.6/en/replication-gtids.html
| url = https://dev.mysql.com/doc/refman/5.6/en/replication-gtids.html
| title = MySQL&nbsp;5.6 Reference Manual, Section&nbsp;17.1.3 Replication with Global Transaction Identifiers
| title = MySQL&nbsp;5.6 Reference Manual, Section&nbsp;17.1.3 Replication with Global Transaction Identifiers
| accessdate = {{date|2015-08-16|mdy}}
| access-date = {{date|2015-08-16|mdy}}
| website = dev.mysql.com
| website = dev.mysql.com
}}</ref> feature of MySQL&nbsp;5.6
}}</ref> feature of MySQL&nbsp;5.6

Revision as of 13:14, 5 April 2021

WebScaleSQL
Developer(s)Facebook, Google, LinkedIn, Twitter and Alibaba Group
Repository
Written inC, C++, Perl and Bash
Operating systemLinux
Platformx86-64
Available inEnglish
TypeRDBMS
LicenseGNU GPL version 2
Websitewebscalesql.org

WebScaleSQL was an open-source relational database management system (RDBMS) created as a software branch of the production-ready community releases of MySQL. By joining efforts of a few companies and incorporating various changes and new features into MySQL, WebScaleSQL aimed toward fulfilling various needs arising from the deployment of MySQL in large-scale environments, which involve large amounts of data and numerous database servers.[2][3]

The source code of WebScaleSQL is hosted on GitHub and licensed under the terms of version 2 of the GNU General Public License.[4][5]

The project website announced in December 2016 that the companies involved would no longer contribute to the project.[6]

Overview

Running MySQL on numerous servers with large amounts of data, at the scale of terabytes and petabytes of data, creates a set of difficulties that in many cases arise the need for implementing specific customized MySQL features, or the need for introducing functional changes to MySQL. More than a few companies have faced the same (or very similar) set of difficulties in their production environments, which used to result in the availability of multiple solutions for similar challenges.[4][7][8]

WebScaleSQL was announced on March 27, 2014 as a joint effort of Facebook, Google, LinkedIn and Twitter (with Alibaba Group joining in January 2015[9]), aiming to provide a centralized development structure for extending MySQL with new features specific to its large-scale deployments, such as building large replicated databases running on server farms. As a result, WebScaleSQL attempted to open a path toward deduplicating the efforts each founding company had been putting into maintaining its own branch of MySQL, and toward bringing together more developers.[2][5][10]

WebScaleSQL was created as a branch of the MySQL's latest production-ready community release, which was version 5.6 as of March 2013. As the project aimed to tightly follow new MySQL community releases, a branching path was selected instead of becoming a software fork of MySQL. The selection of MySQL production-ready community releases for the WebScaleSQL's upstream, instead of selecting some of the available MySQL forks was the result of a consensus between the four founding companies, which concluded that the features already existing in MySQL 5.6 are suitable for large-scale deployments, while additional features of the same kind are planned for MySQL 5.7.[2][4][5]

Features

The initial changes and feature additions that WebScaleSQL introduced to the MySQL 5.6 codebase came from the engineers employed by the four founding companies; however, the project was open to peer-reviewed community contributions.[11] As of September 15, 2014, available new features and changes included the following:[5][10][12][13][14]

  • A software framework that provides automated testing of all proposed changes
  • A customized suite of database performance tests
  • Various changes to the automated tests provided by the MySQL community releases
  • Performance improvements in various areas, including buffer pool flushing, execution of certain types of SQL queries, and support for NUMA architectures
  • Changes related to large-scale deployments, such as the ability to specify sub-second client timeouts
  • Performance and reliability improvements to the global transaction identifier (GTID)[15] feature of MySQL 5.6
  • So-called super_read_only operation mode for the MySQL server, which disables data modification operations even for privileged database accounts

As of March 28, 2014, planned new features and changes included the following:[2][10]

Availability

WebScaleSQL is distributed in a source-code-only form, with no official binaries available. As of March 27, 2014, compiling the source code and running WebScaleSQL is supported only on x86-64 Linux hosts, requiring at the same time a toolchain that supports C99 and C++11 language standards.[5]

The source code is hosted on GitHub and available under version 2 of the GNU General Public License (GPL v2).[4][5]

End of Contributions

In December 2016, the WebScaleSQL website announced the companies originally involved in collaborating on the project (Facebook, Google, LinkedIn, Twitter, and Alibaba) would no longer contribute to the project. The announcement blamed differences among the needs of the various companies for the end of the collaboration.

See also

References

  1. ^ "WebScaleSQL commits history". January 22, 2016. Retrieved December 12, 2016.
  2. ^ a b c d Steven J. Vaughan-Nichols (March 28, 2013). "WebScaleSQL: MySQL for Facebook-sized databases". ZDNet. Retrieved April 1, 2014.
  3. ^ Klint Finley (March 27, 2013). "Google and Facebook Team Up to Modernize Old-School Databases". Wired. Retrieved April 1, 2014.
  4. ^ a b c d Jack Clark (March 27, 2013). "Forkin' 'L! Facebook, Google and friends create WebScaleSQL from MySQL 5.6". The Register. Retrieved April 1, 2014.
  5. ^ a b c d e f "Frequently Asked Questions". webscalesql.org. March 27, 2014. Retrieved April 1, 2014.
  6. ^ "WebScaleSQL Moving Forward". December 29, 2016. Retrieved December 29, 2016.
  7. ^ "Patches for MySQL 5 – MySQL tools released by Google". code.google.com. June 24, 2011. Retrieved April 1, 2014.
  8. ^ "facebook/mysql-5.1". github.com. June 2013. Retrieved April 1, 2014.
  9. ^ "Please welcome Alibaba to WebScaleSQL!". webscalesql.org. January 15, 2015. Retrieved August 15, 2015.
  10. ^ a b c Doug Henschen (March 27, 2014). "Facebook Debuts Web-Scale Variant of MySQL". informationweek.com. Retrieved August 15, 2015.
  11. ^ "Is Your Change Appropriate?". webscalesql.org. March 27, 2014. Retrieved April 1, 2014.
  12. ^ Michael Larabel (March 28, 2014). "Facebook & Others Announce WebScaleSQL". Phoronix. Retrieved April 1, 2014.
  13. ^ Steaphan Greene (March 27, 2014). "WebScaleSQL: A collaboration to build upon the MySQL upstream". code.facebook.com. Retrieved August 16, 2015.
  14. ^ Doug Henschen (September 15, 2014). "Facebook Announces WebScaleSQL Upgrade For MySQL". informationweek.com. Retrieved August 16, 2015.
  15. ^ "MySQL 5.6 Reference Manual, Section 17.1.3 Replication with Global Transaction Identifiers". dev.mysql.com. Retrieved August 16, 2015.
Retrieved from "https://en.wikipedia.org/w/index.php?title=WebScaleSQL&oldid=1016112864"