Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • My concren is whenever end user uses our application it hits our controller so its better to validate the data according to business rules in a controller rather than validating in a model Commented Mar 19, 2012 at 11:34
  • 2
    Its all the same code running in the same place. The overhead of object instantiation and the method calls should negligble or you're doing something seriously wrong. Whilst you shouldn't be blind to performance considerations they really shouldn't be something you worry about in the first instance (in the general case) and more importantly anything that is purely in code is unlikely to be a bottleneck. You will get far more value (and have more time to look at performance if needed) if you have a well structured application with appropriate automated tests Commented Mar 19, 2012 at 12:05