Thread refresh

jordan @jordan@sometimes.social
replies: #2

You are hoping that Redis will go back to its old license, or maybe get forked.

I am hoping that people will start designing the need for Redis out of their applications.

We are not the same.

jordan @jordan@sometimes.social
in reply to #1 - replies: #3

How many data layers are you on, anyway?

@lillian
in reply to #2 - replies: #4

@jordan using redis as a caching layer on top of your database is silly, since said database likely has caching features itself. using redis for temporary data (so, doesn't go in the main database) shared by multiple processes/services is at least somewhat reasonable, I'd say?

jordan @jordan@sometimes.social
in reply to #3 - replies: #5

@lillian Yeah, I don't think using Redis is unreasonable, I just don't like it :D

jordan @jordan@sometimes.social

@lillian At a former workplace, we had a bot that would keep track of every time you used profanity in the chat and post a weekly leaderboard. There were a couple different periods of time where "Redis" would earn you a point.