News for hackers. Stuff that matters.
Re:Open-sourcing Pinterest MySQL management tools by manmtstream on Thursday October 29, 2015 @07:50AM (#10470334)
Looks like a lot of large social media companies are open sourcing their MySQL sharding & management tools lately. This is awesome! My favorite so far is Youtube's Vitess though, since it enables writing dumb clients. The vtgate proxy forwards queries to the right shard similar to Twemproxy. http://vitess.io
Re:Open-sourcing Pinterest MySQL management tools by toomuchtodo on Friday October 30, 2015 @11:46PM (#10481721)
Can Vitess perform connection pooling? Such as aggregating connections from multiple threads locally into one connection to your master or replica?
Re:Open-sourcing Pinterest MySQL management tools by betimsl on Thursday October 29, 2015 @09:30AM (#10470804)
I'm surprised they didn't put a login/signup popup that blocks the entire screen.
Re:Open-sourcing Pinterest MySQL management tools by jroitgrund on Thursday October 29, 2015 @11:52AM (#10471974)
They say they don't use joins, so what's the advantage of using it?
Re:Open-sourcing Pinterest MySQL management tools by frik on Thursday October 29, 2015 @12:07PM (#10472102)
"Zen: MySQL has joined HBase as a supported backend for our graph storage engine."

Is Zen MySQL graph storage open source? Sounds really interesting...

Re:Open-sourcing Pinterest MySQL management tools by rwultsch on Thursday October 29, 2015 @03:24PM (#10473603)
It has not open sourced and I think (and am in no way authoritative) it is unlikely to be open sourced.
Re:Open-sourcing Pinterest MySQL management tools by frik on Friday October 30, 2015 @03:48AM (#10476574)
I would be interested in a blog post how they store graph data in MySQL (star schema?), so that it scales. (an overview article, no technical details)
[dead]
Re:Open-sourcing Pinterest MySQL management tools by rwultsch on Thursday October 29, 2015 @03:22PM (#10473590)
(I am the author)

I wrote most of these tools last year and a lack of good example code definitely slowed me down. Even if we drop support for these tools, at least the code now is open sourced as a reference. This was one of the primary motivations for open sourcing this code.