Data caching strategy

[Ravindra Wankar]

With our in-house ORM, we cache results of queries made using the 
primary key for a table within a single thread. e.g if I fetch user a 
user where ID = 100, this is cached. This ensures that a call from 
another part of the code does not result in an SQL query. Since the 
cache stores the object, any modifications made by a piece of code are 
also available to another.

1. What would be a good place to intercept JOOQ and add similar 
functionality?
2. The other option is to add a loadByPK() method on the Tables which 
calls JOOQ internally and caches the data on return. What would be the 
best way to do this?

Thanks.
- Ravi