Design Patterns Part I

Observer Pattern: This defines a one to many relationship between objects, such that if one object is modified, its dependent objects are to be notified automatically.

For code example you can click here.

Factory Pattern: Creates an object without exposing the creation logic to the client. This uses a class to handle the creation of an object.

For code example you can click here.

MVC Pattern: MVC(Model View Controller) uses separate application’s concerns. Model represents the object that contains the data. View represents the user interface. Controller is the middleman who handles the interaction between the model and view by updating the view whenever the data changes. The controller keeps the model and view separate.

For code example you can click here.

Adapter Pattern: Works as a bridge between two incompatible interfaces. This involves a single class which is responsible to join functionalities of independent or incompatible interfaces.

For code example you can click here.