samus 0.1.1

Volatile memory-store behind a socket server that implements simple CRUD queries
Documentation
  • Coverage
  • 0%
    0 out of 2 items documented0 out of 1 items with examples
  • Size
  • Source code size: 9.06 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 1.14 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 9s Average build duration of successful builds.
  • all releases: 8s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • crates.io
  • Dependencies
    • —
  • Versions
  • Owners
  • stbarrientos

SAMUS

A simple Redis-like volatile memory store behind a socket server.

How to use

Currently, the Samus socket server responds to the following command syntax:

For getting a key: GET <key_name>

For setting a key: SET <key_name> <key_value> <key_ttl>

Note: key values are represented internally as strings. Note: key ttl is given as whole seconds, and is not currently implemented (it will do nothing).

For deleting a key: DELETE <key_name>

Be sure to add a newline character (\n) at the end of your queryies. You can send as many queries as you want as one message (connection) to the socket as a newline seperated list. Make sure to include a trailing newline at the end of the list.

The server will respond with a response to your query. Look for the string __TERM__ in your message. When it appears, the socket server has closed its connection to your client. You will need a new connection to send a new query.

What's next?

  • Message TTL implementation
  • Multi-threaded server capability
  • Refine ergonomics around network protocol