2. Web Architectures Designing for the Web

3. multi-multi-multi-multi-multi Multi-client – PC, Mac, Unix, wireless, … Multi-server-platform – PC, Mac, Unix, watch,… Multi-tier – layers of software components Multi-threaded – concurrent processing Multi-component – CORBA, COM, javabeans,… Multi-database – Oracle, Ingres, Access, … Multi-cultural – North American, European, African, ….

4. Objectives  Examine current web 3-tier client/server architectures  Look at some basic E-commerce architectures

5. Client-Server model and Tiered Architectures  Late 1980’s  Replace centralized mainframe architectures

6. 1-Tier Architecture Processing(a) MainMainFrame

7. File Server Configuration(1-Tier (b)) File Server Files 1.Ask for file 2.File 3.Process 4. Return File

8. Client-Server Architectures  Provide responses rather than file downloads for local processing  Message based  Serves many more users simultaneously  Tiers  2-tier  3-tier  N-tier or multi-tier

9. Client/Server Processing Client Server Data 1.request 2.Process request 3.response

10. 2-Tiers

11. Middle Tier  Implementation Strategies  TP monitors (transaction processing monitors)  Message servers  Application servers  ORB (CORBA) Object Request Broker  Functions  Queuing  Application execution  caching

13. Why bother?  Scalable  Number of users  Number of transactions  Flexible  Drop applications onto different servers  Keep sophisticated applications independent of server

14. Fatness in Clients  Where do you want the processing ??  Fat client  Application and processing on client  Download application and every update  Thin client  Application and processing on server  More traffic

15. Some Design Examples  Shopping cart  B2C  B2B

16. Shopping Cart (B2C) Client Tier (applet/javascript) Validate format of credit card number Do “what-if” calculations Middle Tier/ Middleware (java/perl) Create catalog for display Make purchase Data Tier (Oracle, Ingres, Access, etc) Query inventory for selection of items Update inventory after sale

17. B2B Architecture B2C E-commerce Consumers B2B E-Commerce Business Customers Supplier’s Products Catalog Customer’s Order Information Supplier’s Electronic Mall

18. As a 3-Tier Architecture Supplier GUI Customer GUI Make quote Order Create Catalog Take Order Oracle UI Tier App Tier Data Tier

19. Internet based EDI Internet Web server EDI server database EDI legacy applications Browser

20. Feb 2001C.Watters19 Peer-to-peer Each party has the same capabilities Typically each party is a client-server Examples Napster – MP3 file sharing Gnutella – file sharing IBM APPN

21. Feb 2001C.Watters20 Peer-to-peer on the Internet Transient internet network in which users use the same application to communicate and share access to their hard drives Advantages Don’t have to move files to central server

22. Feb 2001C.Watters21 How to make this work on the Internet Create an application Everybody downloads the application Execute applications Connections Gnutella model – enter known IP address Napster model – enter Napster IP address

23. Feb 2001C.Watters22 Napster and Gnutella MP3 Central server Server collects data Server as switch for downloads Other files No central server Direct IP connections Horizon of 1000

24. Feb 2001C.Watters23 GarageSale Samples Client 1.1

25. Feb 2001C.Watters24

26. Feb 2001C.Watters25

27. Feb 2001C.Watters26

28. Feb 2001C.Watters27

29. Feb 2001C.Watters28

30. Feb 2001C.Watters29

31. Feb 2001C.Watters30

32. Feb 2001C.Watters31

33. Feb 2001C.Watters32

34. Feb 2001C.Watters33

35. Feb 2001C.Watters34

36. RECAP  Internet activity is client/server based  MultiTier architectures provide flexibility  Peer-to-peer is here!