Multi-storage support per keyspace
asilvas opened this issue · comments
Currently every keyspace has an affinity to a single storage account for reads and writes. With multi-storage support, a keyspace could read from one storage account/service, and write to another.
The primary use case is to sit the image api atop public read-only endpoints, and still be able to cache (writes) to a secondary storage. Technically this would also allow multiple reader accounts to store/cache processed images to a single store, if that is the desired pattern.
done