Design and Architecture of Complex Software Systems (DACSS)

Assignment 3: The Broker Pattern

Students can choose one of the following tracks:

Track A: ToyORB: Implement the Broker pattern and realize a small Toy Object Request Broker to allow applications to use remote method invocation. Details track A. This track also contains different optional features that sum up to 4 Bonus points.
Track B: DistributedEventBus: Implement a combination of the EventBus and Broker pattern such that distributed applications can have Publishers and Subscribers in different processes. Details track B. This track has 2 Bonus points.

This assignment puts together 3 lab sessions (corresponding weeks 7, 8 and 9). The duration of this assignment is 3 weeks (results of standard part should be presented no later than week 10). Delays bring a penalty of 1 point for each weeek of delay after the deadline. Optional parts have an extended deadline - week 11.

Code examples are given for:

Using Sockets in Java link
Archive with code to use in your assignment: ByteCommunication.zip
Example with JavaRMI. This RMI example is meant to be an illustration of the Broker pattern. You are not supposed to use JavaRMI, but you must build a "competitor", your own Broker ToyORB in track A of this assignment.
Example with WCF. This WCF example is meant to be an illustration of the remote proxy pattern. You are not supposed to use WCF, but you must build a "competitor", your own Broker ToyORB in track A of this assignment.