-
Type:
Improvement
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: Postponed
-
Component/s: Local Configuration
Currently, we have 2 solutions to define configuration associated to a Document :
- Placeful service
- that is deprecated
- that does not handle cache
- Local Configuration service
- called 4 to 5 times per page
- no cache !
We need to review that and define a better design :
- manage configuration pre-fetch at low level ?
- leverage ES to pre-load information and fill a Redis cache ?
- ....
