Caching Strategy

Hi guys,

I’m starting to leverage caching more and was wondering if the experts can recommend some best practices on where to place the code that does the caching. What i’m trying to avoid is littering my services and handlers with stuff like:

//rough code
if (cacheKey exists){
//use cached object
}else{
//get new object
}

I’m using this within an API, so really I’m mostly dealing with caching objects and JSON.

Questions:

  1. Would event caching come into play at all?
  2. Is there a streamlined way to setup a strategy to cache objects and retrieve objects - (maybe interceptor?)
  3. If I cache something within the API, and then I make a change with another app (admin site) which modifies the data of that object, what is a recommended strategy to purge or rebuild the object within the API?

Thanks!

P.S. Let’s finalize some plans for the ColdBox beer drinking team at CFObjective!

Nolan

Hi guys,

Does anyone have any thoughts on below?

Merci!

Nolan

After vacation. I will. :slight_smile:

We can chat about this when I see you in a few days :slight_smile:

Curt

than put please a summary here and don’t worry, you can leave the drunk parts out :slight_smile: