Briefly explain your solution to Part B and why it works.
What are the average-case, best-case and worst-case number and size of messages being sent as a result of
A PUT message from a client, and
A successful GET message from a client (that is, a value is found and sent back.)
An unsuccessful GET message from a client (that is, no value is found.)
Write a paragraph or two suggesting improvements to scalability that does not compromise your one-node-resiliency.
If your solution provides exactly one-node-resiliency, write a paragraph or two suggesting methods your one-node-resiliency can be expanded to n-node resiliency, assuming your network has time to reconfigure itself in between node failures.
Briefly explain your solution to Part B and why it works.
What are the average-case, best-case and worst-case number and size of messages being sent as a result of
A PUT message from a client, and
A successful GET message from a client (that is, a value is found and sent back.)
An unsuccessful GET message from a client (that is, no value is found.)
Write a paragraph or two suggesting improvements to scalability that does not compromise your one-node-resiliency.
If your solution provides exactly one-node-resiliency, write a paragraph or two suggesting methods your one-node-resiliency can be expanded to n-node resiliency, assuming your network has time to reconfigure itself in between node failures.