Page 14 - DCAP312_WEB_TECHNOLOGIES_II

Web Technologies-II

Notes • Integrity with COM: .NET integrates very well with COM based software. Any COM
component can be treated as a .NET component by other .NET components. The .NET
Framework wraps COM components and exposes an interface that .NET components can
work with. This is absolutely essential to the quick acceptance of .NET, because it makes
.NET interoperable with a tremendous amount of older COM-based software.

1.3.2 Other Benefits of Using .NET Architecture
• The Microsoft .NET platform’s reliance on XML for data exchange an open standard
managed by the World Wide Web Consortium (W3C) and modular XML Web services
removes barriers to data sharing and software integration.
• The .NET platform, through the .NET Framework’s common language runtime, enables
XML Web services to interoperate whatever their source language. Developers can build
reusable XML Web services instead of monolithic applications. By making it easy to offer
your XML Web services to others.
• The ability to easily find available XML Web services means you can buy pieces of your
applications rather than build everything from scratch, focusing your time and money
where it makes the most sense.
• Easier to build sophisticated development tools debuggers and profilers can target the
Common Language Runtime, and thus become accessible to all .NET enabled languages.
• Potentially better performance in system level code for memory management, garbage
collection, and the like have yielded an architecture that should meet or exceed performance
of typical COM based applications today. Fewer bugs, as whole classes of bugs should be
unknown in .NET. With the CLR handling memory management, garbage collection.
• Faster development using development tool like Visual Studio .NET.
1.3.3 N-tier Architecture with .NET

Applications developed in the .NET Framework will still, in, many cases, use a DNA model
to design the appropriate tiers. However, the tiers will be a lot easier to produce in .NET. The
presentation tier will benefit from the new interface technologies and especially Web Forms for
Internet development. The middle tier will require far less COM related headaches to develop
and implement. And richer, more distributed middle tier designs will be possible by using
Web Services.
Let us look into how .Net fit into N-tier architecture. When you talk about a true distributed
N-tier type of application, you are talking about separating the components of the different tiers
on different machines as well as in separate components.

Figure 1.2: N-tier architecture

Tier 1
Client App

Business Rules

http
Tier 3
IIS
Web Service SQL
Server
Data Layer
Tier 2

8 LOVELY PROFESSIONAL UNIVERSITY