InfoQ Homepage   	  		  			  			                  Articles                 		  		GitHub’s Journey from Monolith to Microservices

GitHub’s Journey from Monolith to Microservices

submited by
Style Pass
2021-08-13 21:00:15

InfoQ Homepage Articles GitHub’s Journey from Monolith to Microservices

This article explores GitHub’s recent journey toward a microservices architecture. It takes a deeper look at GitHub’s historical and current state, goes over some internal and external factors, and discusses practical consideration points regarding how we started to tackle this migration. Then we will walk through some key concepts and best practices of implementing a microservices architecture that you can apply as you think about this transformation for your organization.

GitHub was founded in 2008 as a way of making it easier for developers to host and share their code. The founders of GitHub were open-source contributors and influencers in the Ruby community. Because of that, GitHub’s architecture is deeply rooted in Ruby on Rails. Throughout the company’s history, we have employed some of the world’s best Ruby developers to help us scale and optimize our code base.

Today, we have over 50 million developers on our platform, over 80 million pull requests merged per year, and over 100 million repositories across every continent of the world. As you can see, a monolithic architecture got us pretty far. A code base that’s over 12 years old coordinated deploy trains that handle multiple deployments per day, a highly scaled platform serving over a billion API calls on a daily basis, and a fairly performant user interface that focuses on getting the job done.

Leave a Comment