---
title: "Saravana Thiyagarajan (@Saravana-Thiyagaraja) | Hashnode"
description: "Backend Engineer | Emerging Solution Architect Designing and building scalable systems with a focus on performance & reliability."
url: "https://hashnode.com/@Saravana-Thiyagaraja"
---

@Saravana-Thiyagaraja

# Saravana Thiyagarajan

@Saravana-Thiyagaraja · Bangalore,karnataka,India · Joined November 2022

Backend Engineer | Emerging Solution Architect Designing and building scalable systems with a focus on performance & reliability.

## Comments

[The cache invalidation based on the data source which that particular report uses. E.g. : If the report is for sales with particular filter. There can be a new sales entry. Now we invalidate cache & the report query run once again cache it. when will you increment the cache counter in the redis? when every you setting a new value for that particular key which already cached. We increase the version counter. so cache miss would happen on next request which warm the cache up again.](https://hashnode.com/posts/cache-invalidation-the-untold-challenge-of-scalability/69306a22231bd664f42dc180/comment/6930c492f706f000c60d5cc3#reply-69310a7ff1555384b0f8e6a1)

Reply · Article · Dec 4, 2025 · [Cache Invalidation The Untold Challenge of Scalability](https://hashnode.com/posts/cache-invalidation-the-untold-challenge-of-scalability/69306a22231bd664f42dc180)

[Thank you so much for the detailed insight I completely agree, 200%. You’re absolutely right that using a server-side counter misses the causal ordering problem. I initially assumed NTP sync would help, but generating the Lamport clock at the SDK level makes more sense though it adds complexity with restarts and new instances. For now, I’m leaning toward using a Redis-based monotonic counter on the client side to simplify state management, while being mindful of Redis as a single point of failure.](https://hashnode.com/posts/designing-scalable-audit-logging-systems-tackling-clock-drift-and-more/68e776fd043fcc4a3d82c867/comment/68ea2444a3fc7d51efa63924#reply-68ea68d2626fb3062a516d66)

Reply · Article · Oct 11, 2025 · [Designing Scalable Audit Logging Systems Tackling Clock Drift and More](https://hashnode.com/posts/designing-scalable-audit-logging-systems-tackling-clock-drift-and-more/68e776fd043fcc4a3d82c867)

[Uva Prasaath Try to add MFA & Auto token invalidation after certain time. If you have more time. MFA - options security questions T-OPT Push notification to device](https://hashnode.com/posts/building-a-tenant-based-authentication-server-part-i/6795e42fb785c475f0b97926/comment/67979ab87228aa4f25539b84)

Comment · Article · Jan 27, 2025 · [Building a Tenant-Based Authentication Server Part I](https://hashnode.com/posts/building-a-tenant-based-authentication-server-part-i/6795e42fb785c475f0b97926)

[The findings are great. This is what happens even on SSO with some more controls. Under the hood, the same things are happening. Even the session uses a session cookie to maintain a session.](https://hashnode.com/posts/trying-to-understand-google-auth/662fb519fd6ecd5ef8f2138f/comment/662fd96f8983c17c6a445ae2)

Comment · Article · Apr 29, 2024 · [Trying to understand Google AUTH](https://hashnode.com/posts/trying-to-understand-google-auth/662fb519fd6ecd5ef8f2138f)

[I am not sure. You could also consider a rate-limiters based on the unique IP. It could prevent you from system outage.](https://hashnode.com/posts/attack-or-massive-usage/65c29725b265a691d8301678/comment/65c3233e5a485fda94fd5cbe)

Comment · Article · Feb 7, 2024 · [Attack or massive usage?](https://hashnode.com/posts/attack-or-massive-usage/65c29725b265a691d8301678)

[A thought full content Uva Prasaath](https://hashnode.com/posts/building-real-time-experiences/652bf06a717ce769610420b6/comment/652ce184bc306117f3b74ffd)

Comment · Article · Oct 16, 2023 · [Building Real-Time Experiences](https://hashnode.com/posts/building-real-time-experiences/652bf06a717ce769610420b6)

[Uva Prasaath Yes. That's right. But if we want to design a highly scalable system. We want to make our services stateless. So, we can scale it independently without any walk around.](https://hashnode.com/posts/inter-process-communication/651a92dd09a394eb46211498/comment/651ea048429f5cafe9a76cc4#reply-651ea35a554d7eb1e066cb11)

Reply · Article · Oct 5, 2023 · [Inter-Process Communication](https://hashnode.com/posts/inter-process-communication/651a92dd09a394eb46211498)

[It's really a thoughtful article. I want to add more information to solve the shared memory problem in the authentication context. We can use the JWT token to ensure only legitimate users can access it. We don't want to maintain session ID on any kind of database or on the server. Still, we need to maintain a refresh\_tokens on the server.IT can be done by Redis to build a highly scaleable system.](https://hashnode.com/posts/inter-process-communication/651a92dd09a394eb46211498/comment/651ea048429f5cafe9a76cc4)

Comment · Article · Oct 5, 2023 · [Inter-Process Communication](https://hashnode.com/posts/inter-process-communication/651a92dd09a394eb46211498)

[Really a good analogy used for explaining ports on the computer. Great work.](https://hashnode.com/posts/the-magic-doors/64e231d34bf9747a7fcdd4fe/comment/64e2fa2ba217febb971633ac)

Comment · Article · Aug 21, 2023 · [The Magic Doors](https://hashnode.com/posts/the-magic-doors/64e231d34bf9747a7fcdd4fe)

[Thanks dude.](https://hashnode.com/posts/render-props-an-advanced-react-pattern/64bceb051aded2903de12033/comment/64c91667fb80f1a4e44f332b#reply-64c93268fb80f1a4e44f365c)

Reply · Article · Aug 1, 2023 · [Render Props – An Advanced React Pattern](https://hashnode.com/posts/render-props-an-advanced-react-pattern/64bceb051aded2903de12033)
