uniwise / parrot Goto Github PK

Support multiple formats in the REST endpoint:

/v1/project/{project}/language/{language}/{format}

We've settled on using x-trace-id as the header name for request ids. Echo does not allow easy configuration of this, so we probably have to write our own middleware

We should implement a cache purge endpoint. Something like:

POST /project/:project/language/:language/purge

The redis cache should use hset and hget to easier clear translations by project id.

Looks like the service might be throwing 504s for the first couple of seconds of running with a redis cache. Observed one, when rolling the production deployment. The log also hints that the cache is first ready after ~5 seconds of starting the service:

{"level":"info","msg":"Server listening at :80","time":"2021-03-25T09:58:36Z"}
{"level":"info","msg":"Prometheus metrics exposed at :9090/metrics","time":"2021-03-25T09:58:36Z"}
{"level":"info","msg":"sentinel: discovered new sentinel=\"747233771ef03c2613b4ffe2b00157407ca2063d\" for master=\"parrot\"","subsystem":"cache","time":"2021-03-25T09:58:42Z"}
{"level":"info","msg":"sentinel: discovered new sentinel=\"822a5febf7ca75fd42401b3bd12d80512e2701b1\" for master=\"parrot\"","subsystem":"cache","time":"2021-03-25T09:58:42Z"}
{"level":"info","msg":"sentinel: discovered new sentinel=\"b1e9b8d977ca27938692e926b2cce5640e87991e\" for master=\"parrot\"","subsystem":"cache","time":"2021-03-25T09:58:42Z"}
{"level":"info","msg":"sentinel: new master=\"parrot\" addr=\"10.100.77.76:6379\"","subsystem":"cache","time":"2021-03-25T09:58:42Z"}

I propose we include a service healthcheck in the /health endpoint to make sure the cache is ready for reads and writes before routing traffic to it

Add ETag to rest requests to allow for better browser caching.

The ETag could be the MD5 sum of the file.

Assessment frontend build pipeline fetches the terms each time. If we hit a bad cache time (i.e with new changes in POEditor), we would be safe if we could skip cache.