Lect6_client_server.ppt

Software Architectures Instructor Yushan (Michael) Sun Associate Professor Lecture 8: Client/Server Software Architecture 1. Concepts on client-server 2. Evolution of client-server architecture 3. Comparison of 2- and 3-Tier client-server architecture 4. Case Study Definition: Client/Server software architecture is a versatile, message-based and modular Infrastructure that is intended to improve Usability (可用性) Flexibility (灵活性) Interoperability (互操作性), and Scalability (可升级性) A client: A Requestor of Services a piece of software A server: A Provider of Services, a piece of software A client and a server communicate with each other (e.g. by SQL statements) Hardware (Physical separation) is not relevant Platform ( Wintel, Unix…) is not relevant Motivation of client/server architecture: To share resources among many users client interacts with end user server interacts with shared resource(s) One tier Client/Server (mainframe, -1970’s): Host computer that users time-shared (分时) through a terminal that passes keystrokes Huge machines, air conditioning, filled entire room, cost millions of dollars… (IBM, Unisys etc.) Green screens, dumb terminals, legacy systems Post 1960 : Batch systems on mainframe computers collections of jobs made up into a batch example: IBM 1401/7094 2. Evolution of client-server architecture As time passed, corporations separated mainframe-based applications into Client and Server components Characteristics of File Sharing Architecture PC requests file (records) from a file server Business logic all on client, shared resources on server Works when data volume are low 2. Evolution of client-server architecture 2-Tier Client/Server: Databases replaced File Server Word “Client/Server” traditionally associated with desktop PC connected over a network to a SQL-database server Server’s database system (typically RDBMS) can answer a user’s query (SQL) Advantage: Lowered network usage because sen