Merge pull request #2066 from Zerotask/patch-7

docs(cache): add info about using the module globally

Author: kamilmysliwiec

content/techniques/caching.md

@@ -118,7 +118,7 @@ export class AppModule {}
 
 #### Customize caching
 
-All cached data has its own expiration time (TTL). To customize default values, pass the options object to the `register()` method.
+All cached data has its own expiration time ([TTL](https://en.wikipedia.org/wiki/Time_to_live)). To customize default values, pass the options object to the `register()` method.
 
 ```typescript
 CacheModule.register({
@@ -127,6 +127,16 @@ CacheModule.register({
 });
 ```
 
+#### Use module globally
+
+When you want to use `CacheModule` in other modules, you'll need to import it (as is standard with any Nest module). Alternatively, declare it as a [global module](https://docs.nestjs.com/modules#global-modules) by setting the options object's `isGlobal` property to `true`, as shown below. In that case, you will not need to import `CacheModule` in other modules once it's been loaded in the root module (e.g., `AppModule`).
+
+```typescript
+CacheModule.register({
+  isGlobal: true,
+});
+```
+
 #### Global cache overrides
 
 While global cache is enabled, cache entries are stored under a `CacheKey` that is auto-generated based on the route path. You may override certain cache settings (`@CacheKey()` and `@CacheTTL()`) on a per-method basis, allowing customized caching strategies for individual controller methods. This may be most relevant while using [different cache stores.](https://docs.nestjs.com/techniques/caching#different-stores)