This post have been inspired by the talks about controllerless actions. This is NOT an alternative to that. Controllerless actions is an interesting concept that should be study. Actually Jeffrey Palermo has a concept implementation. There is a problem with controllers that grow or contain too much code in them. For the second problem, containing too much code, the only solution I see is code reviews and practice of proper separation of concerns. For the first problem, we can apply some constrains in the way controllers are written and used to limit the number of methods.