The API can use Memcached to cache order book and other information to reduce the load on the database and query time.
We need a pod for this in Kubernetes, but API will also require minor modifications to support it. It's currently hard-wired to use localhost for memcached.
This issue is for tracking implementation of JWS message signing for the API. This necesitates the creation of an APIv2, which should be at https://1btcxe.com/api/v2.
Additional notes for the enhancement:
Should use the same SHA256 API keys as v1 to eliminate the need to re-write the API key generation functionality
Should do signature validation in the frontend code, and not pass any commands back to wlox-api that fail signature validation.
Currently, whenever the DB container is re-created it will start over with a fresh database.. Ideally, we don't want this, but rather we do want it to look for any updated schema files and apply those changes.
Currently, whenever the DB container is re-created it will start over with a fresh database.. Ideally, we don't want this, but rather we do want it to look for any updated schema files and apply those changes.