Your SlideShare is downloading. ×
0
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Presentation6
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Presentation6

514

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
514
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
30
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. IE 20303<br />
  • 2. What is Client/Server?<br />Client<br />Server<br />Network<br />How is client/server different from other distributed computing?<br />Heavy reliance on user-friendly applications<br />Emphasis on centralizing databases and management functions<br />Commitment to openness/modularity<br />Networking fundamental to operation<br />
  • 3. Client/Server Terminology<br />Application Programming Interface (API): A set of function and call programs that allow clients and servers to intercommunicate.<br />Client: A networked information requester (usually a PC or workstation) that can query a database and/or other information from a server.<br />Middleware: A set of drivers, APIs, or other software that improves connectivity between a client application and a server.<br />Relational Database: A database in which information access is limited to the selection of rows that satisfy all search criteria.<br />Server: A computer, usually a high-powered workstation or a mainframe, that houses information for manipulation by networked clients.<br />Structured Query Language (SQL): A language developed by IBM and standardized by ANSI for addressing, creating, updating, or querying relational databases.<br />
  • 4. Client-Server Environment<br />
  • 5. Why is Client-Server Different?<br />Emphasis on user-friendly client applications<br />Focus on access to centralized databases<br />Commitment to open and modular applications<br />Networking is fundamental to the organization<br />
  • 6. Client/Server Applications<br />Emphasis on GUI for users<br />Database Example<br />Database on server, applications for access on client, “glue” (like SQL) enables requests)<br />Application logic can be client-only, or split between client and server<br />
  • 7. Classes of Client-Server Applications<br />Host-based processing<br />Server-based processing<br />Client-based processing<br />Cooperative processing<br />“Thick client” vs“Thin server”<br />
  • 8. 3-Tier Client/Server Architecture<br />
  • 9. Middleware<br />Standardized interfaces and protocols between clients and back-end databases<br />Hides complexity of data sources from the end-user<br />Compatible with a range of client and server options<br />All applications operate over a uniform applications programming interface (API).<br />
  • 10. Middleware Architecture<br />
  • 11. Logical View of Middleware<br />
  • 12. Basic Message Passing Primitives<br />
  • 13. Message Passing Issues<br />Reliability vs Unreliability<br />Reliable facilities guarantee delivery, provide error-checking, retransmission, etc<br />Alternatively, the message can be sent without success/failure; reduces complexity and overhead, passes responsibility for confirmation to application<br />Blocking vs Nonblocking<br />Non-blocking more efficient, but difficult to test and debug programs<br />Blocking (synchronous) retains control until acknowledgment is received<br />
  • 14. Remote Procedure Call Mechanism<br />
  • 15. Client/Server Binding<br />Nonpersistent binding<br />Does not maintain state information, connections re-established as necessary<br />Inappropriate for RPCs used frequently by same caller<br />Persistent binding<br />Connection sustained until procedure return<br />Useful for applications making repeated calls to remote procedures<br />
  • 16. Object-Oriented Mechanisms<br />Clients and servers ship messages between objects.<br />May rely on an underlying message or RPC structure or be developed directly on top of object-oriented capabilities in the operating system<br />Success depends on standardization of the object mechanism, but competing models exist<br />COM, OLE, CORBA<br />
  • 17. Intranets<br />Implementation of Internet-based technologies within an organization, rather than for global connectivity<br />Immensely successful in corporate computing contexts<br />
  • 18. Advantages of Intranets<br />Rapid prototyping<br />Scales effectively<br />Little training required<br />Can be implemented on variety of systems<br />Open architecture allows interaction across platforms<br />Supports a range of distributed servers<br />Allows integration of legacy systems on client and server side<br />Supports a range of media types<br />Inexpensive to implement<br />
  • 19. The Intranet Web<br />Web Content<br />The web can be used to effectively distribute content in a way that requires no new training for end-users<br />Web/Database Connectivity<br />Multiple tools exist to serve as middleware between web servers and data sources<br />Electronic Mail<br />Network News<br />
  • 20. Corporate Intranet Example<br />
  • 21. Web/Database Connectivity<br />Advantages<br />Ease of administration<br />Deployment<br />Development speed<br />Flexible information presentation<br />Disadvantages<br />Limited functionality<br />Stateless operation makes tracking difficult<br />
  • 22. Intranet Webs vs Traditional Client/Server<br />Client/Server Disadvantages Include:1. Long development cycles2. Difficulty in partitioning applications, and modifying based on user feedback3. Effort in distributing upgrades to clients4. Difficult in scaling servers to respond to increased load5. Continuous requirement for more powerful desktop machines<br />
  • 23. Other Intranet Technologies<br />Electronic Mail<br />Closed internal mail systems (delivery verification, etc)<br />Internal mailing lists<br />Network news (USENET)<br />Can be adopted for internal intranet uses<br />
  • 24. Extranets<br />Extends the intranet concept to provide information and services to selected outside populations, such as customers and suppliers<br />Enables the sharing of information between companies<br />A TCP/IP enabled form of EDI<br />
  • 25. Advantages of Extranets<br />Reduced costs<br />Coordination<br />Customer Satisfaction<br />Expedited communication<br />
  • 26. Methods for Converting Intranets to Extranets<br />Long-distance dial-up access<br />Internet access to intranet with security<br />Internet access to an external server that duplicates some of a company’s intranet data<br />Internet access to an external server that originates database queries to internal servers<br />Virtual private network<br />
  • 27. Service Oriented Architecture <br />Client/server architecture utilized widely by enterprise systems<br />Business functions consist of modular structures<br />
  • 28. SOA Architectural Elements<br />Service provider: network node that provides a service interface for a software asset that manages a specific set of tasks.<br />Service requestor: network node that discovers and invokes other software services.<br />Service broker: specific kind of service provider that acts as a registry and allows lookup of service provider interfaces and service locations.<br />
  • 29. Key Characterisitics for Effective Services Use<br />Coarse-grained<br />Interface-based design<br />Discoverable<br />Single Instance<br />Loosely Coupled<br />Asynchronous<br />
  • 30. SOA Example<br />

×