This could make it a more effective replacement for the MemoryStore which just wraps a ruby hash - it could handle in-memory eager syncs in the several hundred megabyte range.
Implement the Store interface using Sqlite, only requiring the file if the Sqlite store is selected via the WCC::Contentful configuration (the same way the Postgres store works)
Sqlite can be loaded in memory using the special filename
:memory:
https://www.sqlite.org/inmemorydb.htmlThis could make it a more effective replacement for the
MemoryStore
which just wraps a ruby hash - it could handle in-memory eager syncs in the several hundred megabyte range.Implement the Store interface using Sqlite, only requiring the file if the Sqlite store is selected via the WCC::Contentful configuration (the same way the Postgres store works)