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*

5
  • see Why do 'some examples' and 'list of things' questions get closed? Commented Jul 20, 2020 at 16:33
  • The quote you reference explains the key difference. Enterprise logic can be shared across systems while business logic is that which typically resides in a single system. Think logging (enterprise) versus order management (business). Commented Jul 20, 2020 at 17:57
  • Thanks @DanWilson, kindly specifiy what are the samples for enterprise logic and business logic Commented Jul 20, 2020 at 18:01
  • 2
    My interpretation of clean architecture is that the domain layer contains all the business rules and the application service layer orchestrates the incoming command by fetching the relevant aggregate, invoking the correct method and persisting the new state. Uncle Bob talks about ‘enterprise wide business rules’ vs ‘application specific business rules’. I haven’t found a need for this distinction yet, maybe someone here has a good example. Commented Jul 20, 2020 at 21:28
  • 1
    var loadedData = LoadDataFromDatabase() - Code calling this method and everything inside this method is enterprise logic. var price = CalculatePrice(loadedData) - code inside this method is business logic Commented Sep 17, 2021 at 4:30