# Why We're Sticking with Ruby on Rails at GitLab

**URL:** <https://forum.devtalk.com/t/why-were-sticking-with-ruby-on-rails-at-gitlab/59015>\
**Category:** Backend In The News\
**Tags:** ruby, rails, gitlab, in-the-news\
**Created:** [10 June 2022 22:36 UTC](https://forum.devtalk.com/t/why-were-sticking-with-ruby-on-rails-at-gitlab/59015 "2022-06-10T22:36:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![CommunityNews](https://forum.devtalk.com/user_avatar/forum.devtalk.com/communitynews/32/1113_2.png) [@CommunityNews](https://forum.devtalk.com/u/CommunityNews)\
**Post date:** [10 June 2022 22:36 UTC](https://forum.devtalk.com/t/why-were-sticking-with-ruby-on-rails-at-gitlab/59015/1 "2022-06-10T22:36:20Z")

</div>

> Why We’re Sticking with Ruby on Rails at GitLab.  
> With our modular monolith, developers can contribute enhancements to the core product, giving us tremendous leverage, unbeatable pace and scalability.

Read in full here:

> **[Why We're Sticking with Ruby on Rails at GitLab](https://thenewstack.io/why-were-sticking-with-ruby-on-rails-at-gitlab/)**
>
> With our modular monolith, developers can contribute enhancements to the core product, giving us tremendous leverage, unbeatable pace and scalability.

_This thread was posted by one of our members via one of our news source trackers._