a.Transaction Script

  1. Motivation
    1. Organizes business logic by procedures where each procedure handles a single request from the presentation
  2. Summary
    1. A Transaction Script organizes all this logic primarily as a single procedure, making calls directly to the database or through a thin database wrapper.
    2. Each transaction will have its own Transaction Script, although common subtasks can be broken into subprocedures.

  3. When to Use
    1. When business logic is not very complex and will not be scalled to much in future.
  4. Overview Tutorials
    1. http://martinfowler.com/eaaCatalog/transactionScript.html
  5. Related Patterns
    1. Domain Model: Prefer Domain Model pattern over Transaction script if your business rules are very complex
  6. References
    1. TODO