As an application grows in popularity and usage you'll need to scale the application to support your new users and their data. One way in which your application may need to scale is on the database level. In this episode, we look at reading from a replica database while writing to a primary database. We also look at structuring our application top support multiple databases; each containing their own schema.

In this episode, we look at various questions asked during interviews.

In this episode, we look at creating a simple and maintainable way to search multiple models. As our application grows and the needs change, other avenues can be explored, but it's important to not prematurely optimize things before they're actually required.

Typically a new Rails application doesn't have much going on, but that can quickly change as the application gets more complex and additional services are added to the stack. In this episode, we look at a few different ways for managing the Terminal for Rails applications.

Abstract super class that provides a thread-isolated attributes singleton, which resets automatically before and after each request. This allows you to keep all the per-request attributes easily available to the whole system.