Four Redis Myths Debunked

Have you heard these rumors about Redis before? Join Justin as he covers the top four misconceptions about Redis, including memory management, scalability, caching, and running your own open source instance vs. letting the pros do the heavy lifting.

Links:

[graffhead]

reading redis docs and redis and action has given me ton of ideas for stuff, like i always wondered how would one scale a raw tcp socket server, typically one stores clients in some sort of array/list/collection etc, that seemed impossible, until i came across redis pubsub, which broadcasts messages across all subscribing clients, that was awesome, and when asking around that seemed to be a common thing, and in socketio one can choose to use redis as a message broker for exactly this thing, now i kind of understand how this all works, i am experimenting with this feature and it has been great.

[SP-yhop]

Is it good idea to have 1 utility micro service for Radis caching or having in all 10+ persist micro services configured with redis interactions. We have like 100+ micro services with Kafka streaming.

[gizmo]

Great video. Myth #2: Is it really a myth for AWS Elasticache Redis, isn't the main difference there that it is not durable or persistent.