u/Different-Cry-8134

do i really need versioning, i researched about versioning and came to know its actually good for future releases, but there are also some examples of some apps(with good scaling) that dont use versioning

so can anyone tell me, how do i get started with versioning my apis in backend and also specify do i really need or not

I just wanted to add shimmer or skeleton loading in my project, but the frameworks for this kind of usecase didnt really crossed my expectations, ui libraries like shad cn have the skeleton component but its really like not being there for the large saas apps, so right now im making separate skeleton components for each component i have , and intuitively this aint going good for managing component, how you guys deal with skeleton loading?

I'm using Refresh Token Rotation (new tokens on every page reload/refresh). My Access Token is in memory, and the Refresh Token is in an HttpOnly cookie.

The Issue:
My database is getting flooded with refresh token entries. Every reload adds a new row, and the table is becoming a performance bottleneck.

How do you handle this?

• Redis vs SQL: Do you move active tokens to Redis to save your main DB?
• One row per user: Do you just UPDATE a single session record instead of INSERTing a new one?
• Concurrency: How do you handle multiple tabs refreshing at once (grace periods)?
• Cleanup: How often are you pruning expired tokens?

Would love to hear how you scale this without the DB lagging!