News for hackers. Stuff that matters.
Re:Rearchitecting GitHub Pages by methyl on Wednesday May 27, 2015 @11:50AM (#9612202)
I'm wondering why GitHub prefers MySQL over PostgreSQL.
Re:Rearchitecting GitHub Pages by samlambert on Wednesday May 27, 2015 @11:56AM (#9612243)
Stable, proven, popular, great roadmap, great replication story, great tooling and an awesome community.
Re:Rearchitecting GitHub Pages by oblio on Wednesday May 27, 2015 @12:07PM (#9612336)
And possibly in-house experience, which is always important.
Re:Rearchitecting GitHub Pages by chralieboy on Wednesday May 27, 2015 @01:03PM (#9612758)
This.

The rest of GitHub runs on MySQL. As the rest of the post alludes, adding unnecessary complexity isn't what they are about (in this case.)

Re:Rearchitecting GitHub Pages by samlambert on Thursday May 28, 2015 @04:49AM (#9616822)
We avoid complexity as much as possible.
Re:Rearchitecting GitHub Pages by brador on Wednesday May 27, 2015 @12:33PM (#9612515)
Would postgreSQL be meaningfully faster?
Re:Rearchitecting GitHub Pages by twic on Wednesday May 27, 2015 @06:40PM (#9614919)
My heuristic is that MySQL is faster for inserts and single-table reads by primary key, but PostgreSQL is faster for more complex queries, particularly if they involve joins or subqueries.

Basically, MySQL is a key-value store in an RDBMS's clothing.

Re:Rearchitecting GitHub Pages by tracker1 on Thursday May 28, 2015 @12:46AM (#9616108)
On the flip side, PostgreSQL's high availability options aren't in the box, or are at the very least varied, problematic and/or cost more than other options for support contracts.

Every time I've worked with mySQL I've seen some irksome behavior... just the same, setting up failover options is miles ahead of PostgreSQL. And when you already have in-house talent, it becomes even more obvious.

My only thought was that using a clustered database (such as Cassandra) as the store with the data itself might have been better. domain/url (minus querystring) would hash/distribute fairly well, and with even a relatively small cluster with 2 replica nodes for the shard would be pretty effective. Also, it would be easier to manage a replicated database, in my mind, than tracking sites to pairs of static servers. GoDaddy is/was moving to something similar with new development on one of their applications when I worked there, and able to serve a huge number of static requests (hundreds of thousands per second) off of a relative few servers with a sub 10ms response time, for content not backed by cdn.

In the end it just goes to show that serving static content on modern hardware can scale really well, with a number of options for technology. Which is why I'm somewhat surprised that something hasn't taken over the tide of poorly configured Wordpress blogs.

Re:Rearchitecting GitHub Pages by samlambert on Wednesday May 27, 2015 @12:36PM (#9612537)
MySQL is extremely fast.
Re:Rearchitecting GitHub Pages by brianpgordon on Wednesday May 27, 2015 @06:12PM (#9614747)
That's... one way of looking at it.

Just because most of the comments here have been (bizarrely) pro-MySQL, I have to link to this article:

http://grimoire.ca/mysql/choose-something-else

Re:Rearchitecting GitHub Pages by nakovet on Wednesday May 27, 2015 @05:00PM (#9614315)
From OP: > we made sure to stick with the same ideas that made our previous architecture work so well: using simple components that we understand and avoiding prematurely solving problems that aren't yet problems

So, if their team have lots of experience with MySQL but not so much with PostgreSQL, that could be a good reason to prefer one over another.

Re:Rearchitecting GitHub Pages by misterbee on Wednesday May 27, 2015 @02:09PM (#9613235)
Full ACID reliability is not mission critical for them.
Re:Rearchitecting GitHub Pages by shlomi-noach on Wednesday May 27, 2015 @03:43PM (#9613822)
Enough with the FUD please. These claims are so 80s. MySQL & InnoDB is fully ACID compliant.