Any user should be able to store data in Redis via bot commands; it is however recommended you ensure that the data storage methods cannot be easily abused. Accidental abuse might happen in the form of many different Redis calls in a short amount of time. For more information on Slack channel spam and remedies, revisit Chapter 2, Your First Bot.
By restricting bot traffic, we can ensure that Redis does not receive an inordinate amount of write and retrieve actions. If you ever find that Redis latency is not as good as it should be, visit this webpage to help troubleshoot: http://redis.io/topics/latency.
Let's now look at how we can improve familiar bot behavior with the addition of Redis data storage.
First, here is our roll command, with the new Redis store code highlighted:
bot.respondTo('roll', (message, channel, user) => {
// get the members of the channel
const members = bot.getMembersByChannel(channel);
// make sure there actually members to interact with. If there...