Provide two implementations of the banking scenario: one using Java RMI and one using gRPC
Design and implement a simplified Remote Method Invocation Framework that enables clients to invoke methods on remote objects as if they were local. As a simplifying assumptions,the remote methods can have parameter and return types limited to Integer and String (can have multiple parameters, but only of these types).
You can choose to implement generation of stubs either statically or dynamically. (Each variant is 1 bonus point. If your implementation supports both methods for stub generation then you can accumulate 2 bonus points).
For details on the architectural components of RPC/RMI middleware and their responsabilities see the slides and discussion in lectures week 6 and 7.
The system must use a custom protocol over TCP sockets and implement explicit marshalling and unmarshalling of requests and responses. You can start from the provided code for a Requestor-Replier which sends and receives bytes over TCP, given in SocketRequestReply.zip. The archive contains the implementation ofthe RequestReply and a simple Echo client-server example using it. You do not have to dig into socket communication, you can use the Requestor sendRequestAndWaitResponse and the Replier start methods while providing a customized implementation of a ByteStreamTransformer.
Demonstrate the usability of your framework by developing two different applications on top of it. One of the applications can be the banking application.