Design ideas for handling configuration

I would like some help thinking about the redis server design. I’ve built until now a server that uses mpsc to handle synchronization of the storage. Until now the storage is just a HashMap that is owned by a thread. The thread can recieve messages using a channel and send back messages through a channel that’s added in the message type. That is I unpack the message and have a sender to respond. Now that I have to add “configuration” I was thinking of doing same thing but it seems that It would become a mess of threads?

I would like some ideas? Thank you :slight_smile:

Ok, maybe you should of read the eventloop design? :smiley: