search

libero / publisher-micro-frontend-experiment

https://github.com/libero/publisher/issues/371
MIT License
0 stars 0 forks source link

Performance #4

Closed thewilkybarkid closed 4 years ago

thewilkybarkid commented 4 years ago

Hard to share caches between the different services, unless something like Varnish is run locally?

Even more API requests [with component-level frontends]...

thewilkybarkid commented 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.

giorgiosironi commented 4 years ago

As long as the architecture is sympathetic to using HTTP correctly, this looks like a deferrable decision?

thewilkybarkid commented 4 years ago

Yep; extending it to private caching is the other thing to bear in mind.

thewilkybarkid commented 4 years ago

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.