Does ember.js encourage too many controllers?
===

I am trying to understand the best practices for structuring an ember.js application. This slide from tomdale:

https://speakerdeck.com/u/tomdale/p/emberjs-more-than-meets-the-eye?slide=55

has a concise description of how to apportion the application logic. However in trying to follow these guidelines I have finding some problems:

1. The router is growing too large. According to the presentation the router "responds to events from views", but this results in a lot of code when there are dozens of views.
2. There are a huge number of controllers. In a Rails application the CRUD actions typically reside in the same controller, however for ember apps it seems that there should be a one controller to list records, one to view a record, one to create a record, etc.

It doesn't feel very DRY because I am ending up with so many files between the controllers, views and handlebars templates that each only have a couple of lines of code.

I am trying to decide if the problem is that I am applying the guidelines incorrectly, or whether these guidelines only work for trivial applications.

Does anyone have any advice - especially on how to manage the growth of the router?
