| |
| |
| |
|
|
| |
| N-Tier |
N-Tier application frameworks allow the presentation GUI, presentation logic tier, business tier, data access tier and data tier to exist separately with on demand union to enable simplified maintenance and management. For instance, any change in the sections of Presentation logic tier like client interface will not require any redo on the code for Business Tier or all the way to database. Just change the presentation logic tier and plug it from anywhere to other tiers. Another instance, You could easily port the Data tier over the new DBMS and touch up some of the code in Data Access tier to use the new system. Even migrating from VB and ASP to VB.Net or C# will just require porting the code over at each tier (phased approach) and then its done.
The tiered approach allows each layer to focus on a specific role -- for example, web servers to serve web pages, application servers to serve business logic components, and a database server to store and serve data. XML, an industry standard lightweight data transfer framework can be used for data transfer within the application layers and with other systems.
|
|
|
|
|
| |
|
|
|
|
