Distributed Information Systems - The Client server model

Slides:



Advertisements
Similar presentations
Distributed Processing, Client/Server and Clusters
Advertisements

ICS 434 Advanced Database Systems
Networks By the end of this session, you will:
Database Architectures and the Web
Distributed Systems 1 Topics  What is a Distributed System?  Why Distributed Systems?  Examples of Distributed Systems  Distributed System Requirements.
Lecture 6.2 System Architecture: Overview IMS1002 /CSE1205 Systems Analysis and Design.
Chapter 10 Site Architecture McGraw-Hill/Irwin Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved.
Data - Information - Knowledge
Distributed components
Technical Architectures
1 Chapter 2 Database Environment Transparencies © Pearson Education Limited 1995, 2005.
1 Pertemuan 13 Servers for E-Business Matakuliah: M0284/Teknologi & Infrastruktur E-Business Tahun: 2005 Versi: >
Revision Week 13 – Lecture 2. The exam 5 questions Multiple parts Read the question carefully Look at the marks as an indication of how much thought and.
Chapter 13 Physical Architecture Layer Design
Ch 12 Distributed Systems Architectures
12 Chapter 12 Client/Server Systems Hachim Haddouti.
The Architecture of Transaction Processing Systems
Distributed Systems: Client/Server Computing
Client/Server Architecture
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 12 Slide 1 Distributed Systems Design 1.
Client/Server Computing. Information processing is distributed among several workstations and servers on a network, with each function being assigned.
Introduction to Databases Transparencies 1. ©Pearson Education 2009 Objectives Common uses of database systems. Meaning of the term database. Meaning.
Client/Server Architectures
System Architecture & Hardware Configurations Dr. D. Bilal IS 592 Spring 2005.
Database Architectures and the Web
1 Chapter 3 Database Architecture and the Web Pearson Education © 2009.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 12 Slide 1 Distributed Systems Architectures.
Database Architectures and the Web Session 5
Lecture On Database Analysis and Design By- Jesmin Akhter Lecturer, IIT, Jahangirnagar University.
CSC271 Database Systems Lecture # 4.
Application Layer CHAPTER 2. Announcements and Outline  Administrative Items  Questions? Recap 1.Introduction to Networks 1.Network Type 2.N etwork.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 27Slide 1 Software change l Managing the processes of software system change.
Slide 1 Physical Architecture Layer Design Chapter 13.
Definitions What is a network? A series of interconnected computers, linked together either via cabling or wirelessly. Often linked via a central server.
Csi315csi315 Client/Server Models. Client/Server Environment LAN or WAN Server Data Berson, Fig 1.4, p.8 clients network.
Introduction  Client/Server technology is seen by many as the solution to the difficulty of linking together the various departments of corporation.
Unit – I CLIENT / SERVER ARCHITECTURE. Unit Structure  Evolution of Client/Server Architecture  Client/Server Model  Characteristics of Client/Server.
Client – Server Architecture. Client Server Architecture A network architecture in which each computer or process on the network is either a client or.
How computer’s are linked together.
Week 5 Lecture Distributed Database Management Systems Samuel ConnSamuel Conn, Asst Professor Suggestions for using the Lecture Slides.
INFS 6225 Object-Oriented Systems Analysis & Design Chapter 11: Physical Architecture Layer Design.
The Client/Server Database Environment Ployphan Sornsuwit KPRU Ref.
Personal Computer - Stand- Alone Database  Database (or files) reside on a PC - on the hard disk.  Applications run on the same PC and directly access.
Advanced Computer Networks Topic 2: Characterization of Distributed Systems.
Networks.
Database Architectures Database System Architectures Considerations – Data storage: Where do the data and DBMS reside? – Processing: Where.
Manag ing Software Change CIS 376 Bruce R. Maxim UM-Dearborn.
CENTRALISED AND CLIENT / SERVER DBMS. Topics To Be Discussed………………………. (A) Centralized DBMS (i) IntroductionIntroduction (ii) AdvantagesAdvantages (ii)
Distributed database system
Data Communications and Networks Chapter 9 – Distributed Systems ICT-BVF8.1- Data Communications and Network Trainer: Dr. Abbes Sebihi.
Chapter 2 Database Environment.
Creating competitive advantage Copyright © 2003 Enterprise Java Beans Presenter: Wickramanayake HMKSK Version:0.1 Last Updated:
CSC 480 Software Engineering Lecture 17 Nov 4, 2002.
Client – Server Architecture A Basic Introduction 1.
CLIENT SERVER COMPUTING. We have 2 types of n/w architectures – client server and peer to peer. In P2P, each system has equal capabilities and responsibilities.
Introduction to Networks. When Personal Computers first appeared in business, software programs were designed for a single user. However as computers.
IT 5433 LM1. Learning Objectives Understand key terms in database Explain file processing systems List parts of a database environment Explain types of.
Lecture 1: Network Operating Systems (NOS)
Distributed Systems Architectures. Topics covered l Client-server architectures l Distributed object architectures l Inter-organisational computing.
Database Architectures and the Web
The Client/Server Database Environment
The Client/Server Database Environment
CSC 480 Software Engineering
#01 Client/Server Computing
Chapter 2 Database Environment Pearson Education © 2009.
Introduction to Databases Transparencies
Database Environment Transparencies
File Operations Access Permissions.
Introduction To Distributed Systems
#01 Client/Server Computing
Presentation transcript:

Distributed Information Systems - The Client server model Week 1 – Lecture 2

Client server model Any computer connected to a network is called a host – (a host for a process which provides or requests a service) The process on a client host requests a service from a process on the server host A process is a program running within a host

Host 1 Client process Server process Server process Client process Proc. A asks Proc. X to Perform a service. Proc. Z asks Proc. C to Perform a service Host 1 does not ask Host 2 to perform a Service Client process Operating system Server process Proc A Proc B Proc C Operating system Server process Proc X Proc Y Proc Z Client process Host 2

Main frame or mini with dumb terminals A brief history of IS 1970’s 1980’s 1990’s 2000’s Main frame or mini with dumb terminals LAN server & PCs 2 tier Client Server 3 & 4 tier Client server

Application layers Presentation Application – the business logic Formatting & displaying data Displaying a form & accepting data Checking the validity of the data entered Application – the business logic Database – storing and locating data File system - recording and reading records on disk

Centralised Dumb terminals Network Mainframe or Minicomputer Basic presentation Dumb terminals Network Form definition Application Database File system Mainframe or Minicomputer

Centralised mainframe or Mini computer Weaknesses Constrained by single server Expensive hardware at the time Strengths Low bandwidth network Architecturally simple Most hardware & system software from the one supplier

PC Lan PCs Network PC Server Presentation Application Database File system PC Server

PC Lan PCs Network File Server Application File system Operating system PCs Application Network Operating system File Server File system

PC LAN Weaknesses Strengths Very high bandwidth – LAN only Constrained by single server Software is distributed Strengths Cheap hardware Provides low cost systems to small organisations with up to 20 users

2 Tier Client server PCs Network Database Server PC or UNIX Presentation Application PCs Network Database Server PC or UNIX Database File system

2 Tier Client server PCs Network Database Server Windows or UNIX Operating system PCs Proc C Application Network Operating system Database Server Windows or UNIX File system Database

Two Tier Client Server Weaknesses Strengths Constrained by single server Distributed software Not scalable Strengths Relatively simple architecture Cheap hardware

3 Tier Client/Server PCs Network Servers Presentation Database File system Application

3 Tier Client/Server PCs Network Presentation Process File system Operating system Presentation Process Proc C PCs Network Operating system Operating system File system Application Process Proc C Database Process

Three Tier Client Server Weaknesses Presentation layer still distributed Complex architecture Strengths Scalable Consistent Performance Lower bandwidth than 4 tier

4 Tier Client/Server PCs Network Servers Browser Database File system Web Application

4 Tier Client/Server PCs Network Browser Process File system Operating system Browser Process Proc C PCs Network Operating system Operating system Operating system File system Application Process Proc C WEB Server Database Process

Four Tier Client Server Weaknesses Browser not designed for TP Perhaps higher bandwidth than 3 tier Complex architecture Strengths Software not distributed Scalable

The Advantages of distribution Scalable Additional servers can be added as needed Open Software components can be replaced or added Heterogenous Software can be in different languages, need different operating systems, run on different hardware Fault tolerant While multiple servers is inherently more likely to result in errors, they also provide redundancy

The advantages of being centralised Architecturally simpler All software and hardware from one supplier Eliminates the overhead of distribution Easier to control security On average, requires less bandwidth

Communications & Networks How does the client host find the server host ? Having found the server host, how are messages reliably passed between them, over telephone lines, wireless links, optical fibre cables? This is the subject matter of communications and networks (weeks 2-5)

Distributed Components How does the client know what server can perform the service? What format does the client use to pass the parameters to the server? Week 6

Integrating disparate systems Organisations have many separate systems Systems in one organisation have to integrate with systems in another Systems are usually developed in complete isolation from each other – often many years apart. They use different data definitions, different coding structures, different data values These systems still have to work together. Week 7 - 9

Security How do we prevent unauthorised users accessing the system? How do we prevent authorised users doing things they should not, or seeing data they must not? How do we identify and authenticate a user? How do we pass messages between systems without those messages being intercepted? Week 10

Server platform There are many different operating systems, computer suppliers, types of middleware etc What are the critical differences? How do we select the right software and hardware to meet our system needs? Week 11

Performance, scalability & reliability Most DIS have many concurrent users How do we design a system to give the required level of performance The number of users and the quantity of data will increase, how do we add hardware and change the software to accommodate those extra users and maintain the required levels of performance & reliability? (week 11)

International differences Users often come from many different countries How does the system adapt to the specific needs of each user Language Character set Legal system Tax laws Currency Week 12

Case study Rory Collins – ex CIO of the ASX Will discuss a major project to implement a new system for the Singapore Stock Exchange Week 12

Next week Basic concepts in computers communicating with each other.