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.

Required fields*

3
  • You answer is very good and its complete, i gave you the bounty for that, however my question was more conceptual. Actually I do believe is better to throw exception from business logic layer, but I need arguments to debate this, that was the goal of my question, because I'm receiving thoughts on my collegues like "throwing exception cause bad performance" or "throwing exception to handle logic is a code smell" that why I really need arguments to discuss that this is the best solution Commented Nov 21, 2016 at 15:06
  • Thanks for the feedback, I tried to describe why it's better to throw exception in Business Logic Layer. It's not controlling the flow of application. It make business logic more reusable and more reliable. It guarantee each unit of work, works the same way always. But if you put business validations in an action method, you may forget to apply the same business validation in another action method which uses the same business logic. Or obviously if you use another service layer, again you should call the same business validations in the new service layer. Commented Nov 21, 2016 at 15:11
  • @Manjar Back to this post after more than 3 years, I can just confirm the answer is the path to go. While what I shared was based on my experience in N-layered architecture, but I can confirm it's the way to go for union architecture or domain driven design as well. Commented Jan 30, 2020 at 15:22