GitLab Blog: We are splitting our database into Main and CI & Why we're sticking with Ruby on Rails.
We are splitting our database into Main and CI to improve the scalability and reliability of GitLab.com.
We are splitting our database into Main and CI
We don’t need microservices
Architecture follows needs, not the other way around.
Luckily, only a tiny part of most codebases is actually performance critical.
Why we're sticking with Ruby on Rails
If you can't build a monolith, what makes you think microservices are the answer?
When tackling a large-scale architecture change, you might find yourself chasing a moving target.