Re: Application logic and Business logic

alex99_at_medcentral.com.au
Date: 02/26/05

  • Next message: mikharakiri_nospaum_at_yahoo.com: "Re: Application logic and Business logic" 
    Date: 25 Feb 2005 17:12:00 -0800

    Vijay Singh wrote:
    > I just read something in EJB design pattern book which baffled me.
    While
    > describing the "Data Transfer Object" pattern, the author said that
    > application logic and business logic should be kept separate from
    each other
    > i,e should be decoupled. I was wondering if anybody can make out what
    he
    > means. Whats the difference between application logic and business
    logic?
    >
    > Thanks
    > Vijay

    The other guys have answered the difference question well enough so I
    won't eloborate.

    Why separate them? EJB's are available to many different applications,
    therefore mixing in one particular app's logic into the business logic
    layer is not appropriate for all the other apps that function
    differently.

    In an n-tier environment, application specific logic needs to be more
    closely tied to each particular application. For that reason you would
    keep the business and app logic separate.

    That said, I agree with topmind, endless useless separation creates
    code that may not even be required or wanted by the customer, bloat.
    You need to draw the line somehow and somewhere. Do I separate business
    and app logic, no. I'll do it when the customer requires (and pays for)
    it.

    Cheers,
    Alex.

  • Next message: mikharakiri_nospaum_at_yahoo.com: "Re: Application logic and Business logic"

    Relevant Pages

    • Re: Decouple SQL queries from class in OOP design
      ... >>> It should be separate from the business rules. ... We need to separate them. ... > This mapping allows us to express the situation as two ordered pairs. ...
      (comp.object)
    • Re: Table Design/Classification, What If ?#1
      ... alternate) from my current table to a separate table... ... What if I have access to a spreadsheet with approx. ... duplicate agent name information from subsequent spreadsheet import updates. ... This is meant for a BUSINESS CONTACT database for myself (I don't want to ...
      (microsoft.public.access.tablesdbdesign)
    • Re: Generic data types in SQL Server
      ... John, ... these are not 'business rules'...these are attributes of customer and ... would most effectively be stored as separate attributes.....overtyping ...
      (microsoft.public.sqlserver.datawarehouse)
    • Re: Separate DAC from BO logic? What about physical assembly?
      ... and how to best logically separate out the ... > Tier of components. ... Then creating a separate tier of Business ... By seperating out the data access ...
      (microsoft.public.dotnet.general)
    • Re: Philosophical question about separating tiers
      ... If you have a business object layer, ... and you connect to objects on another server, ... I understand that by having the business tier separate from the user tier, ...
      (microsoft.public.dotnet.languages.csharp)