# Features at a Glance

* Cache Aggregator
  * Ability to aggregate different caching engines
  * Ability to aggregate different configurations of the same caches
  * Rich aggregation event model
  * Granular logging
* Fast and Simple to use
  * Fast ColdFusion and Java hybrid cache
  * Simple API and configuration parameters
  * Small Footprint
  * No need to create it, configure it or manage it if used within a ColdBox Application
* Solid Core
  * Multi-Threaded
  * Based on [Java Concurrency Classes](http://docs.oracle.com/javase/tutorial/essential/concurrency/)
  * Multiple [Eviction Policies](http://en.wikipedia.org/wiki/Cache_algorithms): LRU,LFU and FIFO
  * Memory Management & Memory Sensitive caching based on [Java Soft References](http://docs.oracle.com/javase/7/docs/api/java/lang/ref/SoftReference.html)
  * High Load Tested
  * Fully Documented
* Extensible & Flexible
  * Cache Listeners for event broadcasting
  * Create your own custom eviction policies
  * Create your own cache providers
  * Create your own CacheBox object storages
  * Extensive and granular purging mechanisms (regular expressions and key snippets)
* Highly Configurable
  * JVM Threshold Checks
  * Object Limits
  * Ability to time expire objects
  * Eternal (singletons) and time-lived objects
  * Object purging based on object usage (Access Timeouts)
  * Fully configurable at runtime via dynamic configurations and hot-updates
* Visually Appealing and Useful
  * Fully featured caching monitor and commands panel
  * Complete cache performance reports


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cachebox.ortusbooks.com/master-1/getting-started/overview/features-at-a-glance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.