Professional Documents
Culture Documents
Client Server Computing Two-tier Architecture Three-tier Architecture N-tier Architecture Evolution of c-s computing in future Conclusion
DUMP TERMINAL
MAINFRAME
STILL PROCESSING ON MAIN FRAME
CLIENT/SERVER
2-TIER
3-TIER
N-TIER
handled all aspects of the network, while each user accessed the main server from a terminal.
The data is processed on the mainframe and then delivered to
the terminal.
The data transfer between the terminal and the mainframe
Personal Computer
Through the years, personal computers started to evolve and
replaced these terminals but the processing is still process on the mainframes.
With the improvement in computer technology, the
Contd
The first PC networks were based on the file sharing.
In file sharing, the server simply downloads or transfers files
Business perspective.
Technology perspective.
Business Perspective
Basically the business perspective should be kept in mind for
For increased productivity. Superior quality. Improved responsiveness. Focus on core business.
The changing business environment. Globalization: The world as a market. The growing need for enterprise data access. The demand for end user productivity gains based on the
Technology Perspective
Technological advances that have made Client/Server computing practical
communication and Internet Database system, operating system and graphical user interface.
Growing cost and performance advantages of PC-based platforms. Enterprise network management.
application to be split into smaller tasks and to perform the tasks among
process. The main operations of the client system are listed below:
Managing the user interface. Accepts and checks the syntax of user inputs. Processes application logic.
Middleware
Middleware is software that runs between client and server
processes.
It is the "glue" between the client and server, which makes it
Client Network
Server
Client machine
Server machine
important criterion, that is, how much of an application is placed at the client end vs. the server end.
Thin Client :
A thin client is one that conducts a minimum of processing on the
client side .
Fat Client :
Fat client is one that carries a relatively larger proportion of processing
load.
Thin server:
This architecture places less application functionality on the server
machine.
For example file servers.
Fat Servers:
This architecture places more application functionality on the
server machine(s).
Typically, the server provides more abstract, higher level services.
Client/Server Application
Has three functional units:
Presentation logic or user interface (for example, ATM
machines)
Business logic (for example software that enables a customer
Two-Tier Architecture
In the two-tier architecture, if the Client/Server application has a number
of business rules needed to be processed, then those rules can reside at either the Client or at the Server.
The architecture of any client/server environment is by definition at least a
two-tier system, the client being the first tier and the server being the second.
The Client requests services directly from server i.e. client communicates
directly with the server without the help of another server or server process.
For bigger, enterprise-class problems, use of this 2-tier approach has
Contd
As the application development is done on client side, maintenance cost of
consuming.
middle tier.
In this structure, when the business activity or business rules change, only
intermediate servers which coordinate the execution of the client request with subordinate servers.
N-tier Architecture
As the 3-tier applications grew more complex, the basic 3 tiers
Contd
Some of the benefits in moving from 3-tier to n-tier is as below:
Easier maintenance and scalability of each tier, independent of the
other tiers
Distribution of processing intensive sub-layers on a separate high-end
processor
Development and deployment of each tier in the most suitable
upper layer for different environments like Web or client application UI.
system
Interoperability - all components (clients, network, servers)
work together
multiple platforms
Ease of application development Lower total costs than mainframe legacy systems. User friendly - familiar point and click interface
Hardware cost
Software cost Complexity
Web.
The emerging Internet-standards-based architecture is Network-
Centric Computing -- Applications that only exist on Networks and that can be
Internet Browsers, Web-TV, Smart-Phones, Personal Digital Assistants (PDA's) and Networked Appliances to harness the virtually limitless power of the Internet.
Net-Centric N-Tier architectures are rapidly becoming the cornerstone for
enterprise application development and companies around the world are adopting it in order to get ahead in the emerging net economy.
Conclusion
N-Tier systems use component based development techniques combined
with the open industry standards of the Internet, to build powerful crossplatform applications which lower costs, are easier to maintain, provide greater efficiencies and fuel competitive advantage.
To Infinity and Beyond! The new thing in the N-Tier model of computing is
the ability to distribute independent objects over as many tiers as makes sense and then link them dynamically, as required, to provide unlimited application flexibility.
Thus The future of client / server computing is to dynamically determine
and assign where the computing resources for an application will reside.
References
http://www.scribd.com/doc/19101563/An-Introductionto-Client-Server-Computing file:///I:/ppt/ppt/Introduction%20to%20N%20Tier%20 Architecture%20Design%20Approach%20%20Developer%20Geeks.htm
Thank you