NestJS yana saida juyɓa caching module (@nestjs/cache-manager) tare da kamfuraɗin juyɓa wanda yake aiki a zaɓuɓɓu ajiyoyin - ajiya-jiya ta tsammani, ko Redis don ajiyar lissafta a gida gidaje multi-instance. Cachiya ɗin ta tasiri sosai ikon aiki ta hanzari hanyoyin aiki masu tsada da maimaita.
({
: [
.({
: ,
: ,
: ,
}),
],
})
{}
@Controller("products")
@UseInterceptors(CacheInterceptor) // automatically caches GET responses
export class ProductsController {
@Get()
@CacheTTL(30000) // override TTL for this route
findAll() {
return this.productsService.findAll(); // result cached; subsequent GETs are instant
}
}
CacheInterceptor yana cache abin amfani na GET endpoint ta atomatik (sakandanawa ta URL) kuma yana yin amfani da sakandanawa a kan bulattar jita-jita — hanya mafi sauƙi don cachiya endpoints masu karantawa.
@Injectable()
export class ProductsService {
constructor(@Inject(CACHE_MANAGER) private cache: Cache) {}
async getProduct(id: string) {
const cached = await this.cache.get(`product:${id}`); // check cache first
if (cached) return cached; // cache HIT
const product = await this.db.findProduct(id); // cache MISS — fetch
await this.cache.set(`product:${id}`, product, 3600000); // store (1h TTL)
return product;
}
}
Inɓewa CACHE_MANAGER yana bada gaggawa cikakke — alƙali-ko-bugi alƙa (bincika cache, kariya zuwa tushe, adana sakandanawa) don caching taƙardar aiki.
CacheModule.registerAsync({
useFactory: async () => ({
store: await redisStore({ url: process.env.REDIS_URL }), // use Redis as the store
ttl: 60000,
}),
});
Jiya jiya daidai kawai, tare da Redis, yana bada raba cache a zaɓun app instance — dole a lokacin da ke gudana multi-instance (cache-jiya-jiya ba a raba tsakanin su).
async updateProduct(id: string, data) {
await this.db.update(id, data);
await this.cache.del(`product:${id}`); // INVALIDATE on change → avoid stale data
}
The biggest caching challenge: INVALIDATION. When data changes, the cache must be
cleared/updated, or users see stale data. Strategies: TTL (accept brief staleness),
explicit deletion on writes (cache.del), or cache tags.
Cachiya shine daya daga babbar samarwa na ikon aiki gida gidaje, kuma juyɓa caching module na NestJS yana sanya shi da tsafta kuma daidai.
Fahamta shi yana da mahimma saboda API masu karantawa ta yawa suna samun fa'ida sosai daga cachiya aiki masu tsada (bubuwan kimanta, kiran API na waje, lissafta) — ta rabawa rabowa jiya kuma rage nauya.
NestJS yana ba da duka auto-caching mai sauƙi (CacheInterceptor na GET endpoints) kuma karfi karura karura (CACHE_MANAGER alƙali-ko-bugi alƙa na taƙardar aiki).
Daidai, juyɓa daidai yana aiki tare da zaɓuɓɓu ajiyoyin, don haka jiya jiya mai iri daya na iya amfani da cachiya-jiya-jiya (sauri, single-instance) ko Redis (raba cache a gida gidaje da yawa) — kuma sani cewa cache-jiya-jiya ba a raba a lokacin girma a jiya gida (yana buƙatar Redis don distributed caching) wannan muhimmin gida garin.
Mai mahimma kamar ma'auni shi ne fahimtar cachiya's mahimman wahala — bulli (share ko sabunta cache lokacin da bayanan suka canja, ta TTL ko delete akai-akai, don girmamata ishe kabbatayya) — tun da rashin kyau da haka shine cachiya rashin nasara.
Fahimta yaya za ka yi kuma lokacin da ya kamata ka yi cachiya, zaɓe daidaitan ajiya na sauki, kuma sarrafa bulli daidai fa'ida jiya ne gida gida ilimi don gina sauri, girma NestJS sabis.