stano45 / hit-or-miss Goto Github PK

Build functions to make communication easier, such as build_set_request(flags, value, ...)

When a request comes at partition, at the moment, it needs to have a key and a value of length 3 (arbitrary number, used just for the first implementation). This is wrong and needs to be changed.

This is where we store the key-value pairs. For each of the entries we implement a struct where we save the data for each of the entries.

We need a queue in order for us to keep track when each entry was called for the partition. The queue has a capacity, when the capacity is reached and a new request is there, the last element of the queue gets dropped.

Make a basic architercture prototype, hook everything up with threads && networking

Create a model for the partition table (ring), provide functions for adding/removing nodes from ring, assigning requests to nodes etc.

Receive notify messages from partitions, add them to ring

When a request comes from the slave node to the partition, it should respond with a hit, miss or error for the request.