Let us quickly review whatever we learnt about Design Patterns in the previous few chapters
• A design pattern describes a proven solution to a recurring design problem, placing particular emphasis on the context and forces surrounding the problem, and the consequences and impact of the solution
• There are 5 design patterns in the SCWCD Exam:
o Value Object Pattern
o Data Access Object Pattern
o Business Delegate Pattern
o Model View Controller Pattern &
o Front Controller Pattern
• The Value Object pattern provides the best way to exchange data across tiers or system boundaries, especially when there is network communication involved. This is a pattern that solves performance issues around network latency
• The DAO pattern provides the connection between the business logic tier and the resource (usually a database) tier. The Data Access Object represents a general interface to the resources layer: It handles all calls to it. JDBC is the most commonly used example of this
• The Business Delegate pattern reduces the dependency between tiers. It is an attempt to make tiers interchangeable so one can access or utilize the services of any other
• The Model-View-Controller architecture compartmentalizes the data and business logic (model) from the presentation (view) from the user action interpreter (controller).
• The Front Controller pattern presents one entry point to a Web site or service. It provides a centralized entry point that controls and manages Web request handling. It eliminates the dependency of the user on a direct resource.
The Key Terms we learnt in the previous few chapters are:
• Design Patterns
• Model-View-Controller
• Value Object
• Data Access Object
• Front Controller
• Business Delegate
Previous Chapter: Chapter 58 - Other Design Patterns
Next Chapter: Self Test - Chapters 51 to 58
Topics Covered in the Blog - Synopsis
Friday, April 29, 2011
Quick Recap: Chapters 51 to 58
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment