In an effort to benchmark Deno KV against other serverless databases, this implements an application split into different services. Each service measures read/write latency to databases and are hosted in a way to ensure that the latency excludes any network latency—by e.g. provisioning both the serverless function in the same AWS region as the respective database.
For more details, check out the blog post summary.
./setup/provision/utils/deploy-deno-kv-backend.sh
./setup/populate/populate-databases.sh
./setup/provision/utils/deploy-deno-kv-frontend.sh
The frontend requires frontend/lib/config.json
to be present for its backend
endpoint in order to invoke the various services. To create the JSON file you
must build out the infrastructure as outlined in the provision README, then
you can run
./setup/provision/utils/update-deno-kv-frontend.sh
which will create the config.json
from the Terraform state file and required
environment variables.