io.stallion.dataAccess.db

Class SmartQueryCache

java.lang.Object

io.stallion.dataAccess.db.SmartQueryCache

public class SmartQueryCache
extends Object

SmartQueryCache is used by the DB singleton to cache query results. Smart cache uses a bunch of heuristics to ensure that a user who has just made an update never sees stale data.

Constructor Summary

Constructors

Constructor and Description
SmartQueryCache()

Method Summary

Modifier and Type	Method and Description
static boolean	checkShouldSkip(String bucket, String key)
static void	clearBucket(String bucket)
static Object	get(String bucket, String key)
static Object	getSmart(String bucket, String key) Under certain conditions, will skip the cache lookup and always return null, thus prompting a cache refresh This is to prevent getting a stale object right after a user has made a POST request.
static void	initCache(String bucket)
static void	load()
static void	set(String bucket, String key, Object value)
static void	shutdown()

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

SmartQueryCache

public SmartQueryCache()

Method Detail

load

public static void load()

initCache

public static void initCache(String bucket)

shutdown

public static void shutdown()

getSmart

public static Object getSmart(String bucket,
                              String key)

Under certain conditions, will skip the cache lookup and always return null, thus prompting a cache refresh This is to prevent getting a stale object right after a user has made a POST request. Otherwise, will hit the cache as normal. By default: * Results are cached for 15 seconds * caching is skipped when run via a task or a job * caching is skipped for non-GET requests * caching is only skipped once per request * caching is skipped if the user made a post request in the last 15 seconds. Thus altogether, if you are getting dozens of GET requests per second, due to a page getting heavy traffic, then the cache will almost always be hit. But if a user has just made some sort of update, they are guaranteed not to get stale data.

Parameters:

bucket -

key -

Returns:

checkShouldSkip

public static boolean checkShouldSkip(String bucket,
                                      String key)

get

public static Object get(String bucket,
                         String key)

set

public static void set(String bucket,
                       String key,
                       Object value)

clearBucket

public static void clearBucket(String bucket)