756204 - kumascript: Implement key prefix for memcache usage

Status: RESOLVED WONTFIX

(developer.mozilla.org Graveyard :: KumaScript, enhancement)

Description

[Les Orchard [:lorchard]]

jakem commented in bug 740093:

> Okay, so we'll need to run a local memcache for the dev node then, because 
> otherwise with a prefix of just "kuma" and "kumascript", dev/stage/prod will all > conflict with each other. This probably won't scale well (in terms of # of
> servers needed), so if it's something we can fix on the 2 apps eventually, that
> would be good. But, developer-dev.allizom.org is just one server, so a local
> memcached will work just fine.

Two possible solutions:

1) Patch node-memcached to support a key prefix, upstream the change to the project. Use a private fork until/unless the upstream pull request is accepted.

2) Intercept memcache calls within kumascript and add a key prefix

Most ideal is #1, assuming the upstream project will accept the patch. If it never does, then we're stuck with a private fork that we'll hopefully keep updated.

Less ideal is #2, which depends less on upstream changes but will probably be a hack.

Comment 1

[Les Orchard [:lorchard]]

Moving this to post-july, because we've discovered that Django 1.2 doesn't support key prefixes either. So, even if kumascript could be moved to memcache servers shared by multiple apps, kuma itself couldn't be

Comment 2

[John Whitlock [:jwhitlock]]

This appears to be about using the same memcache server in different environments (prod / stage / dev). The best practice in 2018 is to run a different server for each environment.