1 / 8

DISRET: A Distributed System To Support a Retail-chain

CS775 PROJECT. DISRET: A Distributed System To Support a Retail-chain. Project Group Srikanth Balusani Rajendra Shirhatti Bhakta Ram. Features of DISRET. Availability -System will work at least with one accessible server. -All Servers in the System will be provided with a

anitra
Download Presentation

DISRET: A Distributed System To Support a Retail-chain

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. CS775 PROJECT DISRET: A Distributed System To Support a Retail-chain Project Group Srikanth Balusani Rajendra Shirhatti Bhakta Ram

  2. Features of DISRET • Availability • -System will work at least with one accessible server. • -All Servers in the System will be provided with a • backup server. • Dynamic System • - System provides for Dynamic Allocation of Resources - Addition/Deletion/Transfer of • Zone, Regional, Retail Servers. • Response Time • - System is designed to provide lowest • response Time

  3. DISRET Architecture National Regional Zonal Retail

  4. Implementation Issues • Communication: • - Remote Method Invocation • Language: • - Java • The modules in the project: • Client: • - Client at each level of Hierarchy • Server: • - Server to serve the Client at Each Level of Hierarchy • Active Resources List: • -Implemented Using XML

  5. DISRET Implementation Local Update Client Server Resource List Lookup Other Servers

  6. Active Resources List <national ncount="1" regc="2" host="stimpy" port="5606"> <REGIONAL host="ren" port="3456" rid="1" zonc="1"> <ZONAL host="dilbert" port="5687" zid="1" locc="1"> <LOCAL host="stimpy" port="343" lid="1" /> </ZONAL> </REGIONAL> <REGIONAL host="ewd" port="3223" rid="2" zonc="0" /> </national>

  7. Design Issues Unresolved Check for Server: - Periodic “ping” of Servers by Server under its Hierarchy - Removal of Resource from Active Resources List if “ping “ fails Election Algorithm: - Implementation of National Server as one of the Regional Servers. - If Regional Server acting as National Fails, implement a Election Algorithm among Regional Servers to find successor. Server to keep track of Requests from Clients: - A Queue Processing Server to keep track of requests from Client, so that requests can be processed in FIFO or Round Robin.

  8. Questions?END OF PRESENTATION

More Related