Network Implications of DDP

Distributed Data Processing : 

Distributed Data Processing By, Jojode Karthik (1020016) Kannan nair (1020017) 1 Networking Implications of

Distributed Data Processing (DDP) : 

Distributed Data Processing (DDP) “A data processing system in which processing is decentralized, with the computers and storage devices in dispersed locations.” “Data processing in which some of the functions are performed in different places and connected by transmission facilities.” 2

Networking Implications of DDP : 

Networking Implications of DDP Connectivity - The ability of components in the system to exchange data Availability - The percentage of the time that a particular function or application is available for users Performance - Response time 3

Functions of Data Processing System : 

Functions of Data Processing System Each distributed computers must include some management and control logic to interact with the central network management system. The work done by any application program can be divided into four general functions: data storage data access logic application logic presentation logic 4

Network Architectures : 

Network Architectures From a viewpoint of distributed application system, there are three fundamental network architectures: Host-based networks Client-based networks Client-server networks Two-tier, Three-tier, and N-tier Architectures 5

Host-Based Architectures : 

Host-Based Architectures The very first data communications network. The clients enabled users to send and receive messages to and from the host computer. This very simple architecture often works very well. Application software is developed and stored on one computer and all data are on the same computer. 6

Client-Based Architectures : 

Client-Based Architectures In the late 1980s. The clients are microcomputers on a local area network, and the host computer is a server on the same network. This simple architecture at low cost often works well. Applications grow, the network circuits can become overloaded. 7

Client/Server Architecture : 

Client/Server Architecture Combine the best aspects of both distributed and centralised computing Users work on powerful workstations or PCs which support end user programming and use of off-the-shelf software Good response time inherent in distributed architecture Cost-effective, e.g. economies of scale by centralising support for specialised functions Flexible and scalable 8

Client-Server Architectures : 

Client-Server Architectures 9

Middleware : 

10 Middleware Client-server networks enable software and hardware from different vendors to be used together. Unfortunately, they have few standards. One solution is middleware, software that sits between the application software on both the client and the server. Middleware does two things: 1. It provides a standard way of communicating that can translate between software from different vendors. 2. It manages the message transfer from clients to servers so that the clients need not know the specific server that contains the application’s data.

Middleware - JDBC : 

11 Middleware - JDBC JDBC(java database connectivity) is Java's version of the DBI module in Perl 5.

Slide 12: 

12 Thank ‘U’