Implement Redis Caching

Maelstromeous commented 8 years ago

We need to create a module which will handle the caching of data to prevent unnecessary queries to Census.

Things that will require caching:

Player UUID (permanently)
Name (long time, should never really change)
OutfitID (short time, this may change quite often for a player)
FactionID (long time / permanent, is probably not possible for devs to even change this)
Battlerank?
Outfits
Outfit UUID (permanently)
Name (permanently)
Tag (short time, this may change repeatedly)
Faction (permanently)
World (permanently)

Maelstromeous commented 8 years ago

Going to use SetEx for 24 hours to keep data as fresh as possible.

Maelstromeous commented 8 years ago

Active Alerts caching implemented.

Maelstromeous commented 8 years ago

The Player and Outfit data is going to be shared with PS2Construction, so I'll have to make sure keys and format are consistent.

Maelstromeous / ps2alerts-ws