'We feel that our MySQL solution still has quite a bit of runway for us, both from a performance perspective and in terms of how much we can store.' 'Even as a monolith, we've been able to scale,' Ma told us. For the foreseeable future we're going to remain with MySQL just because we have a lot of expertise there,' Ma said.įurther, the process of splitting out functional groups into microservices will also enable some breaking apart of the data. 'Similar to Ruby, we have world-renowned DBAs that have scaled a lot of systems. 'We actually have our own version of Ruby that we maintain,' she told us.

They were contributors.' GitHub has also hired leading Ruby developers over the years.

'The founders of GitHub were very deeply rooted in the Ruby community. 'Our strategy is not a complete replacement,' said Ma. 'All that diversity which joined GitHub, which used to be just a Ruby on Rails shop, prompted us to think: how do we enable developers that have brought diversity in tech stack and skill set to be productive working together? That made us realise that the monolith as a sole development option is no longer viable.'ĭoes that mean GitHub is migrating away from Ruby? Internally, we've also merged a few of the sister teams that were within Microsoft, so a lot of folks from Azure DevOps are now part of our team, and they are used to working in anything from C# to TypeScript. And we've acquired Dependabot, NPM which is package management in JavaScript, and Pull Panda. We acquired so many companies, like we've acquired Semmle which is based in Oxford, their primary stuff is in C and Python. 'It really started at the beginning of this year.

The decision is quite recent, Ma told us.

Call of chernobyl monolith war lab code