REST is the core architectural pattern we use to build our Rails applications, but it's not always clear what exactly is and isn't REST. Tune in as Matt Sumner joins Chris to discuss exactly what REST is, and how best to embrace it in your Rails apps.

This is a companion discussion topic for the original entry at


Seems like there is problem with email subject, it says “Intro to SSH” just like in email from previous iteration.
Just thought to let you know.


Thanks for the helpful video!

With avoiding “member” and “collection” in routes, what would be the best way to work with resources that have the same name? Following the download example, what if we wanted to add a download feature for decks as well? There is already a downloads controller, but it’s used for videos. I guess it could always have the name prepended (decks_download and videos_download), but that doesn’t feel as clean with regards to how the routes look. Is there a better way to do this?


1 Like

Hi @mark_kraemer, great question. I think the suggestion you make about specifying in the name makes sense. Likely in a domain where you have multiple types of downloads, you would describe them in words as a “video download” or a “deck download”, so that easily maps to VideoDownloadsController and DeckDownloadsController.

That dude said “right” so many times I got distracted and just started counting the “right’s” spoken.

1 Like