Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Garnet – A new remote cache-store from Microsoft Research

github.com

Post reply on HN
Print view View original

51–60 of 120 posts

Re: Garnet – A new remote cache-store from Microsoft Research

#51

Post by mbreese »

moritonal wrote: post #36
gigatexal wrote: post #33

Earlier quoted context omitted.

Redis for 99% of the intended use-cases and companies will be just fine. It has always been rock solid when we used it. It was the opposite of DNS: it was never a problem.

Could you expand on "It was the opposite of DNS: it was never a problem."? Feel like I'm missing some interesting history here.

It’s just a common saying “the problem is always DNS”. When you have a weird networking issue, the problem always seems to be DNS. Either some misconfigured DNS entry or DHCP giving you the wrong server address, etc…

And then the problem is confounded by the fact that, ironically, DNS works so well that we don’t think of it as a primary point of failure. So inevitably, when there is a DNS problem, it’s the last thing we check. This just reinforces the idea that the problem is always DNS… because in those long, hard to troubleshoot instances… the problem was DNS.

Re: Garnet – A new remote cache-store from Microsoft Research

#54

Post by oaiey »

throwaway38375 wrote: post #52

Neat project, but I will be sticking with Redis. I trust Redis to not do something weird with their licensing or pricing in the future. Plus Redis has billions of production hours under its belt. It's easier to install and understand.

100% on that. I think Garnet (and similar YARP) are useful if you build your own tweaked version of that. Otherwise, off-the-shelf or PaaS thing are more useful.

Also, this is Microsoft Research. This thing is code sharing not a product.

The real interesting part is what Azure will do with it.

Re: Garnet – A new remote cache-store from Microsoft Research

#55

Post by sciurus »

throwaway38375 wrote: post #52

Neat project, but I will be sticking with Redis. I trust Redis to not do something weird with their licensing or pricing in the future. Plus Redis has billions of production hours under its belt. It's easier to install and understand.

The licensing has been through a number of changes in the last few years, depending on which distribution and modules you use.

https://redis.com/legal/licenses/

Re: Garnet – A new remote cache-store from Microsoft Research

#56

Post by dmw_ng »

throwaway38375 wrote: post #52

Neat project, but I will be sticking with Redis. I trust Redis to not do something weird with their licensing or pricing in the future. Plus Redis has billions of production hours under its belt. It's easier to install and understand.

Tech has all the attention span of a goldfish https://techcrunch.com/2019/02/21/redis-labs-changes-its-ope...

Re: Garnet – A new remote cache-store from Microsoft Research

#57

Post by Someone »

throwaway38375 wrote: post #52

Neat project, but I will be sticking with Redis. I trust Redis to not do something weird with their licensing or pricing in the future. Plus Redis has billions of production hours under its belt. It's easier to install and understand.

This is a project from Microsoft Research, so I would worry a lot less about licensing and pricing than about lack of updates (either features, maintenance, or security ones)

Re: Garnet – A new remote cache-store from Microsoft Research

#58

Post by stephenr »

moritonal wrote: post #36
gigatexal wrote: post #33

Earlier quoted context omitted.

Redis for 99% of the intended use-cases and companies will be just fine. It has always been rock solid when we used it. It was the opposite of DNS: it was never a problem.

Could you expand on "It was the opposite of DNS: it was never a problem."? Feel like I'm missing some interesting history here.

People who don't understand networking like to blame DNS for every problem they experience I guess?

Re: Garnet – A new remote cache-store from Microsoft Research

#59

Post by Terretta »

moritonal wrote: post #36
gigatexal wrote: post #33

Earlier quoted context omitted.

Redis for 99% of the intended use-cases and companies will be just fine. It has always been rock solid when we used it. It was the opposite of DNS: it was never a problem.

Could you expand on "It was the opposite of DNS: it was never a problem."? Feel like I'm missing some interesting history here.

Meme this is referencing should be "It's always DNS config."

Re: Garnet – A new remote cache-store from Microsoft Research

#60

Post by CuriouslyC »

LeonidBugaev wrote: post #35
hipadev23 wrote: post #13

Earlier quoted context omitted.

> Redis may require a significant performance optimization. Redis is single-threaded, it’s simple and effective. I’m not sure it needs optimization, and we have 3 alternatives here. Garnet however is the first alternative to actually outperform Redis at both low and high levels of concurrency, which is remarkable. I can’t wait to try it out.

Plus in production, with high load, Redis cluster is way more common, which kind of solve single-threaded concern.

I've always found redis cluster to just bring problems with it.
Post reply on HN