Re:Twitter open sources its MySQL secret sauce
by revelation on Monday April 09, 2012 @05:58PM
(#3819464)
Did I read 'fork'? If you want the open-source cred, make an attempt to get your patches upstream. Google has done it for MySQL (pre-Oracle).
[ Parent
| on HN ]
Re:Twitter open sources its MySQL secret sauce
by jeremycole on Monday April 09, 2012 @08:09PM
(#3819969)
It's a fork in the sense that we're developing without an immediate requirement to get MySQL/Oracle to accept our changes. We hope they will accept the changes, of course, but it isn't and can't be a requirement for our own progress.
Re:Twitter open sources its MySQL secret sauce
by hartror on Monday April 09, 2012 @07:39PM
(#3819864)
It is a fork in that it is a parallel line of development but from reading Twitter's blog the desire is to get some or all of their work upstream. Releasing the fork like this gets them some early OSS & engineering cred while being able to start the conversation on their modifications.
We look forward sharing our work with upstream and other downstream MySQL vendors, with a goal to improve the MySQL community.
http://engineering.twitter.com/2012/04/mysql-at-twitter.html
Re:Twitter open sources its MySQL secret sauce
by polyfractal on Monday April 09, 2012 @06:29PM
(#3819595)
I don't know if it applies in this situation, but certain cases make sense to fork instead of patch. If they are including features that are orthogonal to general MySQL feature set, it shouldn't be patched.
Considering their size and unique requirements induced by that size, I imagine a lot of these changes do not apply to small MySQL installations running WordPress (and in fact may be highly detrimental).
Re:Twitter open sources its MySQL secret sauce
by jeremycole on Monday April 09, 2012 @08:11PM
(#3819977)
I think all of the changes pretty much do apply generally, but for us it's easier to go ahead and publish publically to be able to pass these changes upstream, rather than pass them off privately and wait potentially a year or more to get them back in a public release.
We want to be able to collaborate with Percona, Facebook, Google, MariaDB, etc., on some of the actual changes, to make things better for everyone. This is the first step towards that goal.
Re:Twitter open sources its MySQL secret sauce
by cdibona on Monday April 09, 2012 @11:15PM
(#3820489)
This might be ideal, but it can be very difficult to work with an upstream company like Oracle (who are the copyright holders to MySQL).
Re:Twitter open sources its MySQL secret sauce
by TazeTSchnitzel on Tuesday April 10, 2012 @05:42AM
(#3821450)
Maybe we'll see another LibreOffice?
Re:Twitter open sources its MySQL secret sauce
by furyofantares on Monday April 09, 2012 @06:34PM
(#3819622)
If trying to get their patches upstream doesn't make sense to them internally, it probably won't make sense to others.
Re:Twitter open sources its MySQL secret sauce
by jeremycole on Monday April 09, 2012 @09:24PM
(#3820227)
This is actually not really about whether it makes sense, but about timelines. We expect some of this to eventually make it to upstream MySQL, but likely in a version newer than we need it in (5.6 instead of 5.5) and not for something like a year.
Re:Twitter open sources its MySQL secret sauce
by amateurguru on Monday April 09, 2012 @06:12PM
(#3819515)
Google has their own branch: https://code.google.com/p/google-mysql/
Facebook too: https://code.launchpad.net/mysqlatfacebook