The Cohesion Technology (CT) write-through cache is highly tuned for web-applictions. The cache is in the same memory space as the application for the highest possible performance.

Object level cacheing was chosen over query level caching because query level caching is not able to track the source of each column of information as it is changed in the underlying system.

Cache monitoring tools make it easier to tune cache performance when needed and to adjust table cache parameters to reduce repeated database queries.

Indirect cache indexes maintain a security wall between the user session access controls and the full table record set. Support classes allow indirect access to cached records.

Records are centralized and aged based on table source. Small tables are read in full and larger tables are paged. Modified records are written through the cache to the database.

Despite all of the cacheing a CT run-time has a relatively small memory footprint. Records and complete tablesets age out after a few minutes while often used data remains cached.