Redis explained
architecturenotes.co
Redis explained
1–10 of 104 posts
Re: Redis explained
#2Re: Redis explained
#3I wrote a little post on how Redis works and its various setups! How does everyone setup Redis? Elasticache is a good answer too :P
Re: Redis explained
#4What tool do you use for your diagramming, is it all hand-drawn?
Re: Redis explained
#5Re: Redis explained
#6Re: Redis explained
#7I wrote a little post on how Redis works and its various setups! How does everyone setup Redis? Elasticache is a good answer too :P
[Potentially inaccurate content removed by author]
It's the HN algorithm which is probably due to the fact that other posts from his domain have done relatively well, plus the actual poster here has quite a bit of karma.
Re: Redis explained
#8I see some data-types on the right. It surprises me that redis doesn't have a numeric data type. I understand that at its heart it is just a key-value store and doesn't ever need to do range-based lookup but it still surprises me.
One consequence of "everything is a string" I've run into (although probably a sign I'm "doing it wrong"), is serialisation overhead in the client.
If redis is expecting strings then it's left to the client to choose an appropriate serialisation which can have either performance or other pitfalls.
Re: Redis explained
#9I wrote a little post on how Redis works and its various setups! How does everyone setup Redis? Elasticache is a good answer too :P
[Potentially inaccurate content removed by author]
HN automatically combines submissions so that subsequent submissions count as upvotes for the first submission.
If a popular source posts a new article, users will "rush" to post it to HN to reap that sweet karma and the winner will "catch" the upvotes of the others.