redactedprofile / echo

In Memory Cache Datastore written with Deno

Hi there 👋 My name is Kyle.

I am a web developer by profession, and dabble in game development as a hobby. You will find a mixture of both here.

I keep a general DevLog of all my projects here:

• https://kyle.teamharrison.ca
• https://redactedgames.ca/ky
• and https://ninja-ghost.itch.io

🔭 Currently Working With

^Languages

^Frameworks

^Editors

^API's

📈 Fun Stats:

⚡ Fun fact:

Uh

echo's Issues

Software Crash when Exception thrown, smooth error reporting

Uncaught Exception issue.

On error, the server should not crash, it should instead output an understandable error.

At no point should the server ever crash out of execution, without being manually closed by the user.

Make deliverable Docker image

Using GitHub actions we should be able to compile a Docker image that executes the software with the native deno binary. The docker images can be stored on Github as well.

DockerHub may need to mirror, but it's not the most important part of this right now

Can Echo become an embeddable library for other deno projects?

Is it possible to write Echo in such a way that it can sidestrapped as a library to upload to https://deno.land/x and be includable as an ES6 module in other deno projects?

Worth exploring. It'd just circumvent the server listeners, and just expose the commands as a native API

Persist data to disk

Echo is an in-memory store first and foremost.

However, we can supply a configuration that allows a separate thread on a crontask to snapshot the data tables and store them as a compressed binary to disk in case of a server crash, and an admin wants to restore

removal of the double quotes

Make deliverable binary with Warp

As discussed here on an official Deno issue denoland/deno#986 (comment) it seems that Warp https://github.com/dgiagio/warp is the way to do in compiling an executable native binary

Server crash when client disconnects

error: Uncaught ConnectionReset: An existing connection was forcibly closed by the remote host. (os error 10054)
    at unwrapResponse ($deno$/ops/dispatch_minimal.ts:63:11)
    at Object.sendAsyncMinimal ($deno$/ops/dispatch_minimal.ts:106:10)
    at async Object.read ($deno$/ops/io.ts:39:17)
    at async handle_connection (fi

Command: NUK

NUK is a command that flushes (or: "nukes") the entire database and resets all tables back to default.

• Nukes the Database.

Command: GET

GET command is one that returns the value of a key as it is stored

• Should return the string value verbatim as was stored in the key, if the key exists
• Should return a error if the key doesn't exist or does exist but the TTL has expired

Make command arguments interface objects

Instead of positioned arguments, let's use Interfaces and object spreading as per TypeScript norm.

Command: CHK

CHK is a command that checks if a key is set or not

• Should return a falsy response if the key doesn't exist
• Should return a truthy response if the key exists
• Should return a falsy response if the key does exist by the TTL has expired

Run DEL command on each discovered expired key when invoking is_valid method of KeyObject

currently expired keys just sit the datastore indefinitely

there is a new is_valid routine in the KeyObject class 1075d2b#diff-89e9fd90feb499cac1623bd562b7c8e3R33

This can be universally queried on discovered keys to determine if the key found isn't expired.

Once the #7 is accomplished, we should fire off a new thread to delete the key in the background and simply negate the result from further deliberation

Command: FND

FNS is a command that finds keys that contain a value based on a search query

• Supplying nothing should throw an error
• Supplying a value not wrapped in quotes should throw an error
• Supplying * as the value should return everything
• Supplying mykey* should only return values that start with mykey
• Supplying *mykey should only return values the end with mykey
• Supplying *mykey* should only return values that mykey is apart of in general

Command: TTL

TTL is a command that updates an existing key with a new time to live.

• Supply a truthy value if TTL was updated
• Supply a falsey value if key doesn't exist or TTL is expired.

Command: KEY

KEY is a command that lets you find existing keys based on a search query

• Supplying nothing should throw an error
• Supplying a search value wrapped in quotes should not throw an error as keys cannot exist with a space in them
• Supplying * as the value should return everything
• Supplying mykey* should only return values that start with mykey
• Supplying *mykey should only return values the end with mykey
• Supplying *mykey* should only return values that mykey is apart of in general

TTL command with just key and no value should return remaining seconds

The TTL command as it is designed in #8 is meant as a write only operation

This enhancement is proposed to upgrade TTL from write only to a read value as well and return the time left to live by seconds left

Command: DEL

DEL is a command that allows deleting of one or more keys

• Returns a truthy value is key has been successfully removed
• Allow a comma deliminated list of keys to delete more than one per command
• Allow a fuzzymatch pattern as with #2 to delete keys based on key match
• Return a falsy value if there were any issues

Automate delivery of native binary to various system package managers

Building off of #13

Using GitHub Actions, we can automate creating binaries to various environments.

We should allow updating the binary on different package repositories such as

• apititude
• yum
• choco

Command: SET

SET command simply allows one to create or update a key with a new value

• Returns a truthy value if the key was stored successfully
• If there was an issue, returns a clear error message
• Optionally allow user to supply an inline TTL value without having to execute a follow up command