Download to read offline
Type of Technologies for Distributed Computing
- 1. MTNC-CS UNIT I-INTRODUCTION 1.1CloudComputing at a Glance 1.2 Historical Developments 1.3 Building Cloud Computing Environments 1.4 Computing Platforms and Technologies. Principles of Parallel and Distributed Computing: 1.5 Eras of Computing 1.6 Parallel Vs Distributed computing 1.7 Elements of Parallel Computing 1.8 Elements of Distributed Computing 1.9 Technologies for Distributed Computing.
- 2. 1.9 Technologies forDistributed Computing. 1.9.1 Remote Procedure Call 1.9.2 Distributed Object Frameworks Examples Of Distributed Object Frameworks 1.9.3 Service-oriented Computing 1. 9.4 Service-oriented Architecture (SOA) 1.9.4 Web Services 1.9.5 Service Orientation And Cloud Computing MTNC-CS
- 3. i) Common ObjectRequest Broker Architecture (CORBA) CORBA is essentially a design specification for an Object Request Broker (ORB) that provides an ORB mechanism to allow distributed objects, either locally or on remote devices, written in different languages or in various network locations, to communication with each other. The CORBA Interface Definition Language or IDL enables language development, location-independent interface development and distribution of distributed objects. The application components can communicate with each other via CORBA, regardless of where they are or who designed them. CORBA ensures transparency of the location in order to execute these requests. CORBA is usually described as a "software bus" because the objects are located and accessed via a software communication interface. The following illustration identifies the main components in the implementation of CORBA. MTNC-CS Examples of Distributed Object Frameworks
- 4. ii)Interface Definition Language(IDL) The Interface Definition Language is a key pillar of the CORBA standards. IDL is OMG for the definition of language-neutral APIs and provides a platform- independent line-up of distributed object interfaces. Client / server interface- standardized data and operations begin to provide a consistent approach between the CORBA environments and clients in heterogeneous environments. This mechanism is the IDL and is used by CORBA to describe the object interfaces. iii) IIOP (Internet Inter-ORB Protocol) is a protocol which allows distributed programs to communicate on the Internet in various programming languages. The Common Object Request Broker Architecture (CORBA) is a key element of a strategic industry standard MTNC-CS
- 5. iv)Distributed Component ObjectModel (DCOM/COM) The Distributed component object model (DCOM) is a proprietary Microsoft communication technology between software components that are spread across networked computers. DCOM is a distributed component object model. The Distributed Component Object Model is a component object model (COM) network expansion technology that enables network-wide, interprocess communication. By managing low- level network protocol details, DCOM supports communication among objects within the network. This enables multiple processes to work together to achieve a single task by using distributed programs. MTNC-CS
- 6. vi)Java Remote MethodInvocation (RMI) RMI implies Remote Method Invocation. A mechanism that permits the access / invoke of an object in one program (JVM) on another JVM. It enables remote communication between programs in Java, RMI is used to create distributed applications. We create two programs in an RMI application: the server program (residing on the server) and the client program (residing on the client). The server program creates a remote object and provides the client with a reference to that object (using the registry). The client program requests remote objects and tries to invoke its methods on the server. MTNC-CS
- 7.
- 8.
- 9. Transport Layer− usingthis layer the client are connected with the server. This connection is maintained with existing connection and new connections are also created. Stub − the stub is the proxy of a client remote object. This is located in the client system; it serves as the client's gateway. Skeleton − It's the object on the server side. To pass the request on to a remote object, Stub interacts with the skeleton. RRL (Remote Reference Layer) − this is the layer that manages the client's remote object reference. MTNC-CS
- 10. The following pointssum up how an RMI program works. • Whenever the client makes a request to the remote object, the stub receives the request to the RRL. • If the RRL from the client receives the request, it uses a method called invoke () from the remoteRef object. The request is passed on the server side to the RRL. • The server's RRL passes the client to the server skeleton that eventually calls the object on a server. • The results are passed to the client MTNC-CS
- 11. vii) .NET Remoting •The. NET remote system offers an interprocess communication between Application Domains through the use of the Remoting Framework. • The programs may be installed on the same computer or on different computers on the same network. • Through the use of Binary or SOAP formatters in the data stream the .NET Remoting facilitates distributed object communications over TCP and HTTP channels. • The three main components of the Remoting Framework are: Remote object Remote Listener Application-( Remote Object requests) Remote Client Application-( makes Remote Object requests) MTNC-CS
- 12.