Please enable JavaScript.
Coggle requires JavaScript to display documents.
Design pattern (Behavioral Patterns (Iterator
Sequentially access the…
Design pattern
-
-
MVC Pattern
Models are basically objects, or POJO's to be exact, used as blueprints/models for all of the objects that will be used in the application.
-
Controllers controls both of these. They serve as a connection between the two. Controllers both instantiate, update and delete models, populate them with information, and then send the data to the views to present to the end-user.
-
Composite Entity Pattern
The Composite Entity pattern represents a graph of objects, which when updated, triggers an update for all the dependent entities in the graph.
-
Front Controller Pattern
Upon sending a request, the Front Controller is the first controller it reaches. Based on the request, it decides which controller is the most adequate to handle it, after which it passes the request to the chosen controller.
-
Service Locator Pattern
A pattern often seen in Web Applications, the Service Locator pattern is used to decouple the Service Consumers and the concrete classes like DAO implementations.
Transfer Object Pattern
This pattern is used to transfer objects with lots of fields and parameters in one go. The Transfer Object pattern employs new objects, used only for transfer purposes, usually passed to the DAO.
Creational Patterns
-
-
Object Pool
Avoid expensive acquisition and release of resources by recycling objects that are no longer in use
Object pooling can offer a significant performance boost; it is most effective in situations where the cost of initializing a class instance is high, the rate of instantiation of a class is high, and the number of instantiations in use at any one time is low.
-
-
-