https://eunus.dev/tags/etag/Recent content in ETag onHugo -- gohugo.ioSun, 28 Jun 2026 00:00:00 +0600https://eunus.dev/blog/version-based-cache-validation-in-abp-keeping-the-application-layer-clean-without-redis/Sun, 28 Jun 2026 00:00:00 +0600https://eunus.dev/blog/version-based-cache-validation-in-abp-keeping-the-application-layer-clean-without-redis/Every caching tutorial I found did the same thing: reach into the application service, wrap the method body in GetOrCreateAsync, and call it clean architecture. The service now knows it’s being cached. It has a cache key. It has an invalidation call in the delete method. It has become a caching service with a thin layer of business logic underneath. That bothered me. The application layer is supposed to contain orchestration and business use cases — not decide whether a response came from memory or a database.