hasjob icon indicating copy to clipboard operation
hasjob copied to clipboard

Cache session active_at in Redis for periodic job processor

Open jace opened this issue 8 years ago • 0 comments

This branch introduces two new patterns that need some discussion and consensus on:

  1. Models that store frequently changing data (like active_at timestamps) in Redis, for periodic job processors to flush to database. Should we override the column property to transparently write to Redis instead of custom code each time? Should the flush to db have a standardised name like say flush_from_redis?
  2. Models that use UUID keys and must expect queries with either UUID or string parameters. Where exactly is type safety enforced?

jace avatar Jun 03 '16 12:06 jace