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.
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.
User experience is important and there are little things that we can do to help improve this experience. By giving real time feedback on text inputs to approaching limits on fields, the user can modify and update their text accordingly before they submit the form. In this episode, we look at database level, model validations and limiting text input on the client side.
Using Scenic, you can bring the power of SQL views to your Rails application without having to switch your schema format to SQL. Scenic provides a convention for versioning views that keeps your migration history consistent and reversible and avoids having to duplicate SQL strings across migrations.
Seeding your database is often an overlooked part of development and it has a lot of benefits that can help uncover issues within your application. However, maintaining the seeds.rb can be difficult and things can get out of hand quickly. In this episode, learn how to manage and maintain the seeds file.