3 ms·
If you ever want to scale your app to more than one process (CPU core), or more than one server, you'll have a problem... Using Redis could be a solution (if R
by weddpros 10y ago
If you ever want to scale your app to more than one process (CPU core), or more than one server, you'll have a problem...
Using Redis could be a solution (if Redis can accommodate your read pattern), or you'll need a pub/sub system (like that of redis) to propagate db changes from one process to the other...
- Kiro 10y agoThanks! I'm building a real-time app using WebSockets so a pub/sub system sounds like a good solution.
- elmigranto 10y agoPostgres has it with LISTEN/NOTIFY. It also can read from and write to Redis using Foreign Data Wrappers. Pretty neat, if you want your DB to be single place you store data, but something faster for reads or cache.