Data caching
implement data caching for frequenly used data:
(may require subissues)
-
Graph Data for Neo4j
- Cache graph nodes and edges fetched from the backend (
Neo4jGraphView
). - Example: Store fetched graph data locally to avoid repeated backend calls when switching labels or refreshing the graph.
- Cache graph nodes and edges fetched from the backend (
-
Character Data
- Cache character lists retrieved from MongoDB (
CharacterTable
). - Example: Store character data locally to reduce API calls when editing or deleting characters.
- Cache character lists retrieved from MongoDB (
-
Player Statistics
- Cache player statistics fetched from Cassandra (
PlayerStatForm
). - Example: Use local storage or state management to persist player stats between page reloads.
- Cache player statistics fetched from Cassandra (
-
Active Players
- Cache active player states retrieved from Redis (
PlayerState
). - Example: Store active player data locally to avoid fetching it repeatedly.
- Cache active player states retrieved from Redis (
-
Node Labels for Filtering
- Cache Neo4j node labels fetched for filtering (
Neo4jGraphView
). - Example: Store labels in memory to avoid fetching them every time the graph view is loaded.
- Cache Neo4j node labels fetched for filtering (
-
Quest Data
- Cache quests retrieved from MongoDB (
CharacterTable
). - Example: Store quest data locally for faster access during character updates.
- Cache quests retrieved from MongoDB (