Why we're sticking with Ruby on Rails

This post explains the rationale behind GitLab's continued use of Ruby on Rails, highlighting its benefits for approachability, productivity, and modularity. It contrasts Rails' 'modular monolith' approach with the complexities and potential pitfalls of microservices, advocating for the former as a more pragmatic solution for most organizations. The post also touches upon how Rails' architecture supports GitLab's open-core business model by providing a well-structured codebase for community contributions. Performance-critical components are identified as areas where other technologies (Go for Gitaly, PostgreSQL for persistence) are leveraged, demonstrating a pragmatic approach to technology choices.