Answer chapter (12)

1-Explain why distributed systems are inherently more scalable than centralized systems? What are the likely limits on the scalability of the system?

A distributed system is scalable if it remains effective as the number of users and/or resources increase
Controlling resource costs o Grows as the number of users increases Controlling performance loss o Increases with number of users o Hierarchic structures have better search times than linear structures Preventing resources from running out o Difficult to predict o Adjusting better than overcompensating? Large IP addresses increase storage demands Avoiding performance bottlenecks o Some resources accessed frequently o Decentralize algorithms E.g., Domain Name Service o Replication & caching

2-What is the fundamental difference between a fat-client and a thin-client approach to client-server systems development? Explain why the use of Java as an implementation language blurs the distinction between these approaches. ANSWER:

In a fat-client system, some of the application processing is carried out on the client whereas in a thin client system only the user interface is displayed on the client and all of the application processing is carried out on the server. Java blurs the distinction as it allows the development of applets which can be downloaded to the client at execution time. Depending on the functionality of the applet, this allows a degree of control over the processing that is carried out on the client.

3-Your customer wants to develop a system for stock information where dealers can access information about companies and can evaluate various investment scenarios using a simulation system. Each dealer uses this simulation in a different way, according to his or her experience and tile type of stocks in question. Suggest a client-server architecture for this system that shows where functionality is located. Justify the client-server system model that you have chosen? ANSWER:

Since the simulation is carried out different way between dealers and all the crucial parts are the data of each stock and company information, it is effective the develop a fat-client model where the server holds the data and the application is in the users desktop. It is a swift approach where user can request a consistent data and simulate it under the application which resides in the user computer.

4-By making reference to the application model shown in Figure 12.4. discuss problems that might arise when converting a 1980s mainframe legacy system for insurance policy processing to a client-server architecture.What are the basic facilities that must be provided by an object request broker? ANSWER:

Lack of system documentation and obsolete system that is not used anymore might bring a problem to understand the program flow. Client-server application needs to define which function for application processing or data management to be separately reside in client or server respectfully. Lack of function clarity might cause difficult to effectively design the system architecture. Presentation layer might mixed up in the other layer which may difficult to edit the presentation layer globally. (Different presentation for different function)

Or
A problem might arise because there is no clear separation between the presentations, application-processing, and/or data management layers. In older systems, these usually are all intertwined and it may be difficult to disentangle these systems to produce the required separation. Presentation, application-processing, and/or data management layers must be mapped on two computers systems, the client and server. There may be either problem with scalability and performance if this thin-client model is chosen; it is one of the methods of client-server architecture. Problems with system management is chosen if the fat-client model is used another method of client-server architecture.

12.5 What are the basic facilities that must be provided by an object request broker?

Answer: The Object Request Broker (ORB) manages interaction between clients and servers. This includes the distributed computing responsibilities of location, referencing and 'marshalling' of parameters and results.

The CORBA specification defines an architecture of interfaces and services that must be provided by the ORB, no implementation details. These are modular components so different implementations could be used, satisfying the needs of different platforms. The ORB manages the interactions between clients and object implementations. Clients issue requests and invoke methods of object implementations.

6-Explain why the use of distributed objects with an object request broker simplifies the implementation of scalable client-server systems. Illustrate your answer with an example.

ANSWER:
In a fat-client system, some of the application processing is carried out on the client whereas in a thin client system only the user interface is displayed on the client and all of the application processing is carried out on the server. Java blurs the distinction as it allows the development of applets which can be downloaded to the client at execution time. Depending on the functionality of the applet, this allows a degree of control over the processing that is carried out on the client.

Or
The use of distributed objects and an ORB simplifies the implementation of scalable systems as it is very easy to add additional servers in the form of distributed objects to the system. These can be introduced without perturbing other parts of the system. An example would be a web server which can be easily replicated as the number of users increases.

6-How is the CORBA IDL used to support communications between objects that have been implemented in different programming languages? Explain why this approach may cause performance problems if there are radical differences between the languages used for object implementation. ANSWER:

CORBA IDL will create a standard format to be used between the languages. Thus the definition, offset and orientation of each of the parts is defined by the IDL. Then the IDL compiler will translate that information into the correct structures for each language. This can cause performance hits if the languages (or machines) are of a radically different architecture. Then a lot of time can be lost converting between the two formats