|Eduardo Freitas 9665db2f39||1 year ago|
|application||1 year ago|
|middleware||1 year ago|
|.gitignore||1 year ago|
|LICENSE||1 year ago|
|readme.org||1 year ago|
This is supposed to be a simple RPC middleware written in GoLang for my "Distributed Systems" class.
The middleware will (maybe) respect design patterns and implement infrastructure, distribution and common services layers. There will be a client request handler, server request handler, requestor and marshaller. This is the "application neutral" part, where the middleware will not change acoording to the application/remote object. Then there is the client proxy and invoker, that relates directly to the application, wether its the client or remote object.
The application will be a simple "weather" app. Previously, I made a weather application using OpenWeatherMap, implemented in GoLang's RPC. But performing an application performance evaluation was very difficult since the time measurament depended on the request and reply from openweathermaps' service. Since the class goal is to develop a middleware and compare its performance to existing ones, the application should depend only on the middleware, for simplicity's sake. So, in this scenario, there will be no real weather. The application will generate a fake struct containing some weather data and send to the client. This will be done so that the implementation can be done locally, and performance evaluation can evaluate only the middleware performance.
Client Request Handler (application neutral)
Server Request Handler (application neutral)
Requestor (application neutral)
Marshaller (application neutral)