1 / 12

Ivan Marsic Rutgers University

LECTURE 20: Distributed Computing Broker and Middleware. Ivan Marsic Rutgers University. Topics. Middleware Broker Design Pattern Java Remote Method Invocation (RMI). Object Messaging via Middleware. Serialization / Marshalling.

caraf
Download Presentation

Ivan Marsic Rutgers University

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LECTURE 20: Distributed Computing Broker and Middleware Ivan Marsic Rutgers University

  2. Topics • Middleware • Broker Design Pattern • Java Remote Method Invocation (RMI)

  3. Object Messaging via Middleware

  4. Serialization / Marshalling • From software objects to a sequence of bits for network transmission Computer A Computer B Client List Sorter Middleware Middleware Network List 010110011

  5. Middleware • Middleware is a collection of objects that offer a set of services related to object communication, so that extraneous functionality is offloaded to the middleware • To reduce the number of object’s responsibilities • In general, middleware is software used to make diverse applications work together smoothly

  6. Middleware Object A Object B (a) Middleware Object A Object B' Object A' Object B (b)

  7. Broker Pattern (a) (b)

  8. Broker Class Diagram (c)

  9. Client-Server RMI/RPC

  10. Java RMI Example

  11. Practical Issues • Do not design for patterns first • Reaching any solution is the priority;solution optimization should be secondary • Refactor the solution to patterns • E.g., to reduce the complexity of the program’s conditional logic • Uncritical use of patterns may yield worse solutions!

More Related