Why we're sticking with Ruby on Rails

What this post added

This post elaborates on GitLab's continued commitment to Ruby on Rails, highlighting its architectural benefits such as approachability, productivity, and modularity, which enable a modular monolith. It contrasts this with the complexities and costs of microservices, advocating for the 'boring' and well-structured nature of a monolith. The post also touches upon performance optimizations through external services like Gitaly and PostgreSQL, and how Rails' structure supports GitLab's Open Core business model by making the codebase approachable for contributors.