There are three basic classifications of patterns Creational, Structural, and Behavioral patterns. Creational Patterns • Abstract Factory :- Creates an instance of several families of classes • Builder : - Separates object construction from its representation • Factory Method :- Creates an instance of several derived classes • Prototype :- A fully initialized instance to be copied or cloned • Singleton :- A class in which only a single instance can exist Note : - The best way to remember Creational pattern is by remembering ABFPS (Abraham Became First President of States). Structural Patterns • Adapter :-Match interfaces of different classes . • Bridge :-Separates an object’s abstraction from its implementation. • Composite :-A tree structure of simple and composite objects. • Decorator :-Add responsibilities to objects dynamically. • Façade :-A single class that represents an entire subsystem. • Flyweight :-A fine-grained instance used for efficient sharing...
An Object-Oriented Database Management System (OODBMS), sometimes referred as Object Database Management System (ODMS) is a Database Management System (DBMS) that supports modeling and creation of data as objects. OODBMS provides support for object classes, class property and method inheritance by sub classes and their objects. A Relational Database Management System (RDBMS) is also a DBMS but, that is based on the relational model. Most popular DBMSs currently in use are RDMSs. As mentioned earlier RDBMS is based on the relational model and data in a RDMS are stored in the form of related tables. So, a relational database can simply be seen as a collection of one or more relations or tables with columns and rows. Each column corresponds to an attribute of the relation and each row corresponds to a record that consists of data values for an entity. RDMSs are developed by extending hierarchical and the network models, which were two previous database systems. Main elements of a RD...
Here are some points that differentiate ASP.NET WebForms from ASP.NET MVC: ASP.NET WebForms ASP.NET MVC Uses the ‘Page Controller’ pattern. Each page has a code-behind class that acts as a controller and is responsible for rendering the layout. Uses the ‘Front Controller’ pattern. There is a single central controller for all pages to process web application requests and facilitates a rich routing architecture Uses an architecture that combines the Controller (code behind) and the View (.aspx). Thus the Controller has a dependency on the View. Due to this, testing and maintainability becomes an issue. ASP.NET MVC enforces a "separation of concerns". The Model does not know anything about the View. The View does not know there’s a Controller. This makes MVC applications easier to test and maintain. The View is called before the Controller. Controller renders View based on actions as a result of the User Interactions on the UI. At its core, you ‘canno...
Comments
Post a Comment