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...
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...
Relational databases like SQL Server use indexes to find data quickly when a query is processed. Creating and removing indexes from a database schema will rarely result in changes to an application's code; indexes operate 'behind the scenes' in support of the database engine. However, creating the proper index can drastically increase the performance of an application. The SQL Server engine uses an index in much the same way a reader uses a book index. For example, one way to find all references to INSERT statements in a SQL book would be to begin on page one and scan each page of the book. We could mark each time we find the word INSERT until we reach the end of the book. This approach is pretty time consuming and laborious. Alternately, we can also use the index in the back of the book to find a page number for each occurrence of the INSERT statements. This approach produces the same results as above, but with tremendous savings in time. When a SQL Server has ...
Comments
Post a Comment