Closed thewilkybarkid closed 4 years ago
For eLife we used caching at the code level, with it stored in Redis. The implementation is pretty basic, and isn't shared.
Might be an idea to run a Varnish in front of each back-end service, and allow private caching. This needs care, and can easily be optional for basic usage.
As long as the architecture is sympathetic to using HTTP correctly, this looks like a deferrable decision?
Yep; extending it to private caching is the other thing to bear in mind.
The other aspect is the front-end, which is being covered by https://github.com/libero/publisher-micro-frontend-experiment/issues/3.
Will close this.