This evening I flipped the switch such that we're now a production user of redis - the fast in-memory key-value store.

The current split looks like this:

• MySQL for:
  • All articles, user-data, and account information.
• Redis for:
  • All login sessions.

This is a test of using redis "for real". If it works out then we'll probably migrate away from MySQL and store comments, users, and article text in Redis itself.

However even without that mixing "persistent" data alongside "transient" data always felt wrong. So I'm glad that is separated.