CLIENT SERVER

ARCHITECTURE

1
 Overview Of Different
Architectures

Introduction
1. Client/Server Architecture
2. File Sharing Architecture
3. Mainframe Architecture
4. Distributed /collaborative enterprise architecture

2
Main Frame architecture
1. With Mainframe software architectures
all intelligence is within the central
host computer
2. A limitation of mainframe software
architectures is that they do not easily
support graphical user interfaces or
access to multiple databases from
geographically dispersed sites

3
File Sharing Architecture
1. The original PC networks were
based on file sharing architectures
2. File sharing architectures work if
shared usage is low, update
contention is low, and the volume
of data to be transferred is low

4
Client/Server Architecture

1. As a result of the limitations of file

sharing architectures, the
client/server architecture emerged
2. A Database server replaced the File
server
3. Network traffic was reduced, because
user queries could be answered
directly.

5
 Types of Client/Server
Architectures
Two Tier Architecture
Three Tier Architecture

6
 Two Tier Architecture

Architecture
1. User Interface (requester of services)
2. Server Interface (provider of services)

Advantages
1. Improves Scalability

7
Two-Tier Architecture cont.
1. Non-Complex
2. Non-time Critical information
processing system
3. User Interface in User side, database
management in the server side

8
 Two Tier Architecture Cont.
 Disadvantages

1. Performance Detoriats if more than 100

users are involved
2. Interoperability is limited
3. System Administration is difficult

9
 Usage of Two Tier Architecture
1. Two tier software architectures are used
extensively in non-time critical information
processing
2. This design is used frequently in decision
support systems where the transaction load is
light.

10
 Continued….
3. The two tier architecture works well in
relatively homogeneous environments with
processing rules (business rules) that do not
change very often and when workgroup size
is expected to be fewer than 100 users, such
as in small businesses.

11
 Three Tier Architecture

Architecture

 Advantages:
1. It overcomes all the disadvantages of Two
Tier Architecture, by providing a middle layer
12
 Three Tier Architecture cont.
 Disadvantages:
1. The development environment is more
difficult to use, than the Two Tier
development environment
2. The cost involved is much more than the
Two tier Architecture

13
 Three Tier Architecture cont.
Usage of Three tier Architecture :

1. Used in distributed Client/Server

Architecture. That provides flexibility,etc.
2. Used in Internet applications
3. Used in net-centric applications

14
 Different Implementations
Three-tier architecture with transaction
processing monitor technology

1. The basic type of Three Tier Architecture

2. The middle layer consists of Transaction
Processing [TP] monitor technology.
3. This focuses on the intelligence in the
monitor
15
 Different Implementations cont.

Three Tier with Message Server

1. This consists of headers

2. This focuses on Intelligent messages
3. Good solutions for wire less infrastructure

16
Different implementations cont
Three tier with an Application Server

1. Application Oriented
2. Application runs on a shared environment
3. Hence less security to worry about
4. This architecture can be used, when
Security, Scalability, Cost are the major
considerations
17
 Different Implementations cont.

Distributed /collaborative enterprise

architecture
1. An enterprise is defined , as a system
comprised of multiple business systems or
subsystems

18
 Conclusion
Usage Considerations
Cost Limitations
Dependencies
Alternatives
Complementary Technologies

19
 Bibliography:
1. "Client/Server Computing--Architecture, Applications and
Distributed Systems Management” by Bruce Elbert, Bobby
Martyna
2. "Client/Server Architecture” by Alex Berson
3. Dickman, A. "Two-Tier Versus Three-Tier Apps."
InformationWeek 553 (November 13, 1995): 74-80.
4. Gallaugher, J. & Ramanathan, S. "Choosing a Client/Server
Architecture. A Comparison of Two-Tier and Three-Tier
Systems." Information Systems Management Magazine 13, 2
(Spring 1996): 7-13.
5. Edelstein, Herb. "Unraveling Client/Server Architecture."
DBMS 7, 5 (May 1994): 34(7).
6. Newell, D.; Jones, O.; & Machura, M. "Interoperable Object
Models for Large Scale Distributed Systems," 30-31.
Proceedings. International Seminar on Client/Server
Computing. La Hulpe, Belgium, October 30-31, 1995. London,
England: IEE, 1995 20