sequelize-simple-cache
This is a simple, transparent, client-side, in-memory cache for Sequelize.
Cache invalidation is based on time-to-live (ttl).
Selectively add your Sequelize models to the cache.
Works with all storage engines supported by Sequelize.
This cache might work for you if you have database tables that
(1) are frequently read but very rarely written and
(2) contain only few rows of data.
In a project, we had a couple of database tables with a sort of configuration.
Something like 4 or 5 tables with some 10 rows of data.
Nearly every request needed this data, i.e., it was read all the time.
But updated only very rarely, e.g, once a day.
So, pre-fetching or simple in-memory caching would work for us.
If that's not matching your scenario,
better look for something more sophisticated such as Redis or Memcached.
Tested with
- Sequelize 6, Node 12/14/15, integration tested with Postgres 11/12 (via pg 8) and sqlite3 v5 (memory)
- Sequelize 5, Node 10/12/13, integration tested with Postgres 10/11 (via pg 7) and sqlite3 v4 (memory)
Install
npm install sequelize-simple-cache
Usage
Setup the cache along with loading your Sequelize models like this:
const Sequelize = require('sequelize');
const SequelizeSimpleCache = require('sequelize-simple-cache');
const sequelize = new Sequelize('database', 'username', 'password', { ... });
const cache = new SequelizeSimpleCache({
User: { ttl: 5 * 60 },
Page: { },
});
const User = cache.init(require('./models/user')(sequelize));
const Page = cache.init(require('./models/page')(sequelize));
const Order = cache.init(require('./models/order')(sequelize));
const fred = User.findOne({ where: { username: 'fred' }});
./models/user.js
might look like this:
const { Model } = require('sequelize');
class User extends Model {}
module.exports = (sequelize) => User.init({ }, { sequelize });
More Details
Supported methods
The following methods on Sequelize model instances are supported for caching:
findOne
, findAndCountAll
, findByPk
, findAll
, count
, min
, max
, sum
.
In addition, for Sequelize v4: find
, findAndCount
, findById
, findByPrimary
, all
.
Non-cacheable queries / bypass caching
You need to avoid non-cacheable queries, e.g., queries containing dynamic timestamps.
const { Op, fn } = require('sequelize');
Model.findAll({ where: { startDate: { [Op.lte]: new Date() }, } });
Model.findAll({ where: { startDate: { [Op.lte]: fn('NOW') }, } });
Model.noCache().findAll(...);
Model.findOne({ where: { name: 'foo' }, transaction: t, lock: true });
Time-to-live (ttl)
Each model has its individual time-to-live (ttl), i.e.,
all database requests on a model are cached for a particular number of seconds.
Default is one hour.
For eternal caching, i.e., no automatic cache invalidation, simply set the model's ttl
to false
(or any number less or equals 0
).
const cache = new SequelizeSimpleCache({
User: { ttl: 5 * 60 },
Page: { },
Foo: { ttl: false }
});
Clear cache
There are these ways to clear the cache.
const cache = new SequelizeSimpleCache({...});
cache.clear();
cache.clear('User', 'Page');
Model.clearCache();
Model.clearCacheAll();
By default, the model's cache is automatically cleared if these methods are called:
update
, create
, upsert
, destroy
, findOrBuild
.
In addition, for Sequelize v4: insertOrUpdate
, findOrInitialize
, updateAttributes
.
You can change this default behavior like this:
const cache = new SequelizeSimpleCache({
User: { },
Page: { clearOnUpdate: false },
});
If you run multiple instances (clients or containers or PODs or alike),
be aware that cache invalidation is more complex that the above simple approach.
Bypass caching
Caching can explicitly be bypassed like this:
Model.noCache().findOne(...);
Limit
This cache is meant as a simple in-memory cache for a very limited amount of data.
So, you should be able to control the size of the cache.
const cache = new SequelizeSimpleCache({
User: { },
Page: { limit: 30 },
});
Logging
There is "debug" and "ops" logging -- both are off by default.
Logging goes to console.debug()
unless you set delegate
to log somewhere else.
event
is one of: init
, hit
, miss
, load
, purge
or ops
.
const cache = new SequelizeSimpleCache({
}, {
debug: true,
ops: 60,
delegate: (event, details) => { ... },
});
Unit testing
If you are mocking your Sequelize models in unit tests with Sinon et al.,
caching might be somewhat counterproductive.
So, either clear the cache as needed in your unit tests. For example (using mocha):
describe('My Test Suite', () => {
beforeEach(() => {
Model.clearCacheAll();
});
Or disable the cache right from the beginning.
A quick idea... have a specific config value in your project's /config/default.js
and /config/test.js
to enable or disable the cache respectively.
And start your unit tests with setting NODE_ENV=test
before.
This is actually the way I am doing it; plus a few extra unit tests for caching.
const config = require('config');
const useCache = config.get('database.cache');
const cache = useCache ? new SequelizeSimpleCache({...}) : undefined;
const model = require('./models/model')(sequelize);
const Model = useCache ? cache.init(model) : model;