Distributed configuration
1 / 29

Distributed Configuration - PowerPoint PPT Presentation

  • Uploaded on

Distributed Configuration. T.C Software + T.C. Hardware = One OS in a multiprocessor system (DOS) Communication : shared memory T.C. Software + L.C. Hardware = Homogeneous OS in network (DOS) Communication : message passing

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'Distributed Configuration' - ena

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Distributed configuration l.jpg
Distributed Configuration

  • T.C Software + T.C. Hardware = One OS in a multiprocessor system (DOS) Communication: shared memory

  • T.C. Software + L.C. Hardware = Homogeneous OS in network (DOS) Communication: message passing

  • L.C. Software + L.C. Hardware = Heterogeneous OS in network (NOS) Communication: file sharing, network commands

Nos dos5 l.jpg


  • L.C. Software + L.C. Hardware + Middleware:

  • NOS->DOS :

  • near really distributed system + complexity reduction

Middlewares l.jpg

  • 1. distributed file systems

  • file level transparency (remote file using)

  • 2. RPC

  • process level transparency (remote procedure call)

  • 3. distributed objects

  • object level transparency (remote object call)

  • 4. distributed documents (web)

  • document level transparency (remote document call)

Slide8 l.jpg

T.C. software + L.C. hardware ->T.C software + T.C harwarewhy?communication by shared data(control mechanisms: semaphores , monitors)is easiercommunication by message(control mechanisms : algorithms:reliable group communication)

Multiprocessor architectures l.jpg
Multiprocessor architectures

  • A multiprocessor traffic control system

Characteristics l.jpg

  • Simplest distributed system model.

  • System composed of multiple processes which may execute on different processors.

  • Architectural model of many large real-time systems.

  • Distribution of process to processor may be pre-ordered or may be under the control of a dispatcher.

Characteristics15 l.jpg

-The application is modelled as a set of services that are provided by servers and a set of clients that use these services.

-Clients know of servers but servers need not know of clients.

-Clients and servers are logical processes

Characteristics18 l.jpg

  • Presentation layer

    • presenting the results of a computation to system users and with collecting user inputs.

  • Application processing layer

    • providing functionality e.g., in a banking system, banking functions such as open account, close account, etc.

  • Data management layer

    • managing the system databases.

Characteristics20 l.jpg

Thin:Used when legacy systems are migrated to client server architectures. The legacy system acts as a server with a graphical interface implemented on a client.

Fat:suitable for new C/S systems where the capabilities of the client system are known in advance.

More complex than a thin client model.

New approach using mobile code applet activex l.jpg
New Approach(using mobile code: applet, activex

Fat + Thin: A 3-tier C/S architecture

Characteristics23 l.jpg

  • each of the application architecture layers may execute on a separate processor.

  • -better performance than a thin-client approach and is simpler to manage than a fat-client approach.

  • -A more scalable architecture - as demands increase, extra servers can be added.

Characterictics l.jpg

No distinction between clients and servers.

Each distributable entity is an object that provides services to other objects and receives services from other objects.

Object communication: a middleware:ORB.

More complex to design than C/S systems.

Advantages l.jpg

allows to delay design decisions: where and how services should be provided.

a very open system architecture: new resources to be added to it.

The system is flexible and scaleable.

reconfigure the system dynamically with objects migrating across the network as required.

A data mining system l.jpg
A data mining system

  • new types of relationship to be mined by adding new integrator objects.