:rocket: Best practices for scaling Rails
Do not scale prematurely. Many of these add complexity. Also, do not do all of them. Evaluate each of them independently for your application.
Keep the majestic monolith as long as possible. Spend a good amount of time fixing pain (app boot times and test times are common sources). Microservices or multiple self-contained systems add a huge amount of complexity.
Assign different teams as owners for different parts of the code for things like triaging errors. Do not discourge other teams from working in that part of the code. Ownership can help with this.
Max out your existing technologies before introducing new ones. Even if your current technology isn’t the perfect fit for the job, there’s a huge cost associated with learning and operating something new.
The database is often the primary bottleneck when scaling.