network_system_architectures

network_system_architectures - IEG 4180 IEG 4180 Network...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: IEG 4180 IEG 4180 Network Software Design and Programming Network Software Design and Programming Architectures for Network Systems Architectures for Network Systems IEG4180: Network Software Design and Programming - Architectures for Network Systems 2 Copyright Jack Y. B. Lee All Rights Reserved Contents • 1. Introduction • 2. Sub-System Types • 3. Client-Server Architecture • 4. Multi-Tier Architectures • 5. Web-based Multi-Tier Systems • 6. Decentralized Architectures IEG4180: Network Software Design and Programming - Architectures for Network Systems 3 Copyright Jack Y. B. Lee All Rights Reserved Data 1. Introduction • First, we have isolated systems: End-user e.g. running dBase • Then, we have file-shared systems: Data End-users File Server Network e.g. Netware / Windows NT e.g. running dBase IEG4180: Network Software Design and Programming - Architectures for Network Systems 4 Copyright Jack Y. B. Lee All Rights Reserved 1. Introduction • Next comes client-server systems: Data End-users Application Server e.g. SQL Server Network SQL Applications • and decentralized systems … Peer Peer Peer Peer Peer Peer Peer Peer Peer Peer Peer Peer Peer IEG4180: Network Software Design and Programming - Architectures for Network Systems 5 Copyright Jack Y. B. Lee All Rights Reserved 1. Introduction • Network System Architecture ¡ Division into Functional Components Network Application Sub-System B Sub-System C Sub-System A Purposes: 1. Hardware/software platform compatibility. 2. Interfacing / integration with legacy systems. 3. Security 4. Reliability (e.g., fault containment) 5. Performance (e.g., scalability) Sub-systems may run in the same or separate hosts. IEG4180: Network Software Design and Programming - Architectures for Network Systems 6 Copyright Jack Y. B. Lee All Rights Reserved 2. Sub-System Types • Client – the end-user application. • Server – the application serving clients. • Agent – an application working for a client. • Proxy – an application working on behalf of a client. • Gateway – an application performing translation or adaptation services. News Reader News Server News Server NNTP Web-News Gateway Web Browser HTTP HTTP Proxy HTTP Web Browser HTTP NNTP NNTP A sub-system can be both a client and a server. IEG4180: Network Software Design and Programming - Architectures for Network Systems 7 Copyright Jack Y. B. Lee All Rights Reserved 3. Client-Server Architecture • Types of Servers ¡ Data Server (Output Only) • Serves primarily data stored/captured at the server. • E.g., web server, file server, and media server. ¡ Information Server (Processing + Output) • Serves query for information and return results after processing....
View Full Document

This note was uploaded on 05/18/2010 for the course INFORMATIO IEG 4180 taught by Professor Jacky.b.lee during the Spring '09 term at CUHK.

Page1 / 44

network_system_architectures - IEG 4180 IEG 4180 Network...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online