How v-barros/sider works
Project Type and Purpose
• It listens on a TCP port, parses incoming RESP commands, executes them against an in-memory hash table, and returns RESP-formatted responses.
File Structure
• Top-level C modules map to logical components:
• networking.c/.h + connection.c/.h → socket management & client I/O
• eventloop.c/.h → reactor pattern for multiplexed I/O
• resp_parser.c/.h + parser.c/.h + commands.c → protocol decoding & command dispatch
• ht.c/.h → in-memory hash table (data store)
• server.c/.h → bootstrap, configuration, wiring all components
• utils.c/.h + string.c/.h → helper routines
• No build directories—Makefile drives compilation, LICENSE and README stand alone.
README for Additional Insights
• README is minimal, so architecture must be reverse-engineered from modules.
• No external dependencies or services, all runtime functionality lives in this single process.