Network Architecture

Network Architecture

1

Introduction • • • •

Selecting a Network Architecture Peer-to-Peer Networks Client-Server Networks Hybrid Networks

2

Selecting a Network Architecture • Network Architecture – The way in which computers participate in a network. • The type of architecture chosen by an organisation may include geographical location, number of users, the requirements of specific application packages, level of technical support available, existing systems, and of course cost etc 3

Peer-to-Peer Networks

Hub

Stations, No Server, Equal Priority 4

Peer-to-Peer Networks • Resources shared in a de-centralised manner • Shared resources include files and printers • Should be used where nodes less than ten • Files are not stored centrally, e.g. Morpheus • Allows easy node-to-node communication

5

Peer-to-Peer Networks • Support is usually part of OS • Sharing of files is responsibility of each participant • Participants form a ‘Workgroup’ • Workgroup is assigned a name – important where there are multiple workgroups (eg dept.s)

6

Selecting a Peer-to-Peer Network • Research the current situation • Employees have little or no network experience • Use with less than ten nodes • Does not require a server • No Network Manager available • Little concern about security 7

Advantages • Easy to configure • No requirement for server hardware/software • Users can mange their own resources • No need for a network administrator • Reduce total cost

8

Disadvantages • • • • •

Provide a limited number of connections May slow performance of nodes Do not allow central management Do not have a central store of files Users responsible for managing own resources • Offers very poor security 9

Security on Peer-to-Peer Networks • Uses share-level security • Allows password protection of resources • Options are: • Give access to all • Assign a single password and give to all users who require access to the resource

• With share-level security a password can not be assigned to a single individual – it assigned to the resource (soon everyone knows what the password is). 10

Implementation • NICs for each computer • Cable media to connect PCs (options) • A Hub has ports for connecting the cables from each computer • Software with the OS should allow sharing of files, directories, disks, printers, scanners, fax modems etc • Note – Windows ’98 and Apple Macs can use their serial port instead of a NIC (much slower) 11

Implementing under Windows • Windows ’95 & ’98 near identical • Windows ME/2000 use a wizard • Install: • NIC • Protocol (try NetBUI) • File and Printer Sharing

• Right mouse click to allow sharing of resources 12

Client-Server

13

Client-Server Networks • Most common architecture • Sometimes ‘next step’ after an organisation has outgrown peer-topeer • Centralised model for data storage, security, running applications and network administration 14

Client-Server Networks • • • •

Based on a scaleable model Users network servers Provide services such as printing, email etc Allow a high level of security to be implemented • Can be centrally managed

15

Client-Server Terminology • Applications Programming Interface (API) • Client • Middleware • Relational Database • Server • Structured Query Language (SQL) 16

Why is Client-Server Different? • Emphasis on user-friendly client applications • Focus on access to centralized databases • Commitment to open and modular applications • Networking is fundamental to the organization

17

Client-Server Pros & Cons • Advantages • Networked web of computers • Inexpensive but powerful array of processors • Open systems • Grows easily • Individual client operating systems

• Disadvantages • Maintenance nightmares • Support tools lacking • Retraining required

18

Generic Client/Server Architecture

19

Database Client/Server Architecture

20

Classes of Client/Server Architecture

21

3-Tier Client/Server Architecture

22

Middleware • Standardized interfaces and protocols between clients and back-end databases • Hides complexity of data sources from the end-user • Compatible with a range of client and server options • All applications operate over a uniform applications programming interface (API). 23

Middleware Architecture

24

Logical View of Middleware

25

Middleware Mechanisms • Message-Oriented Middleware • Remote Procedure Calls • Object Request Brokers

26

Remote Procedure Call Mechanism

27

Object-Oriented Mechanisms • Clients and servers ship messages between objects. • May rely on an underlying message or RPC structure or be developed directly on top of object-oriented capabilities in the operating system • Success depends on standardization of the object mechanism, but competing models exist • COM, OLE, CORBA

28

Multiserver Networks • Each server provides a different service (or duplicates to provide redundancy) • Typically 50 – 500 users • Improves performance • Servers optimised for their service • Much more complex than single-server

29

Enterprise Networks • Supports thousands of users across company’s geographical locations • May involve hundreds of servers • Each location looks like a simple clientserver system, but is linked to the corporate network • A WAN extends the client-server model across many LANs (involving several servers to satisfy a request) 30

Hybrid Networks • Incorporates the best features of workgroups in Peer-to-Peer with the performance, reliability and security of server-based systems. • Allows access to central resources, but also allows users to function at the Peer-to-Peer level • Users do not have to log in to a central server

31

Hybrid Networks – Advantages • Client-server apps are still centrally managed • Users can assign loacl access to their resources • Workgroups can manage resources without need for assistance from network administrator

32

Hybrid Networks – Disadvantages • Network access can become burdensome • Users required to remember multiple passwords • Files can be duplicated !! • Files stored on the workstation are not backed up

33