How I accidentally use Redis (sort of)
Redis. I bet every software developer has heard of or used Redis in their project at some point. Or learn about it at least for the technical interview. However, not many have had the chance to use or utilize it as I have. Up to this point, I just know that Redis is an in-memory key-value store that can be used to implement queues and pub/sub messaging. Let me re-catch what Redis is. Redis is an open-source, in-memory, NoSQL key-value store used as a database, cache, and message broker. It's an all-around software that can be used to cache or even as a database (please don't do this).
Redis help increase my API performance
- 0–1s — Instant Response: Users expect immediate feedback or they assume the app is broken.
- 1–3s — Acceptable Wait: Users tolerate a short delay if a loader or animation is shown.
- 3–7s — Attention Drift: Users start losing focus and may shift attention elsewhere.
- 7–15s — Drop-Off Zone: Most users abandon the task unless it’s very important.
- 15s+ — Abandonment: Users fully disengage and won’t return to the action.
