2 ms·
You're not wrong about anything. Is this a technology I would only use when building websites at scale or something? Basically, though I'd amend that to r
by JohnBooty 7y ago
You're not wrong about anything.
Is this a technology I would only use when building websites at scale or something?
Basically, though I'd amend that to read "websites that might need to scale at some point."
For a lot of projects, shared memory is a perfect choice. But if you might need to scale up to multiple instances at some point, shared memory obviously won't do. And since it's not like there's a huge penalty for using Redis, a lot of times it's just convenient to use it from the beginning.
- qes 7y ago> And since it's not like there's a huge penalty for using Redis There is compared to shared memory. If you actually need to scale and don't have an in-memory cache layer over Redis you're likely going to get hurt.
- core-questions 7y agoThe real solution here is to simply write your code with an appropriate amount of abstractions, and then start with the simplest / cheapest backend that fits your needs. When it comes time to add Redis, or shared memory, or both, only a small amount of your code needs to be adjusted for the new backing store.