The statements that Redis doesn’t need multi-threading because generally Redis is not CPU bound it’s network bound is utter total bullshit. I’ve benchmarked it. It cannot realize full network capacity with its current single threaded design.
-
-
Replying to @kellabyte
There is more in the blog post, and is that IMHO the right way to full utilize the machine is too coordinate multiple share nothing instances. So the goal is to improve such coordination. You can disagree but please report the whole idea not the half you choose to.
1 reply 1 retweet 33 likes -
Replying to @antirez @kellabyte
Matthew S. Wilson Retweeted Matthew S. Wilson
Indeed, partitioning and decoupling is often a simpler path to scale, compared to scaling up a single {program,system} where dynamic interactions are harder to reason about.https://twitter.com/_msw_/status/1093292119567917056 …
Matthew S. Wilson added,
4 replies 0 retweets 5 likes -
Running multiple instances is in fact a simple way to scale a piece of software but it isn’t the only way and it also comes with some very limiting tradeoffs.
1 reply 3 retweets 33 likes -
I think this is my new favorite tweet
1 reply 0 retweets 0 likes -
Replying to @ricky_hartmann @kellabyte and
Throwing away density for convenience is ok as long as it's an economic time/value/SLI call - for many systems/businesses it's the right call. The corollary also holds true. For Redis, license instability is a bigger adoption barrier today though...
1 reply 0 retweets 0 likes -
Replying to @darachennis @ricky_hartmann and
Core Redis is BSD licensed, and it has a diverse base of copyright holders (including non Redis Labs employees) so re-licencing would take effort and individuals signing off. So let's clear the FUD?
1 reply 0 retweets 4 likes -
Replying to @_msw_ @ricky_hartmann and
True and acknowledged, and I'm conflicted ... but the latest licensing trend is a pair-programming with a lawyer shitshow I just don't want to visit again ...
1 reply 0 retweets 1 like -
Replying to @darachennis
I think that it's highlighting how important understanding your software supply chain is. When you bring something into your stack, it's important to not only understand the license, but also if there is a sustainable community or a strong commitment to remaining open source.
1 reply 0 retweets 6 likes -
Replying to @_msw_
Yep! And license churn brings lawyers back into the fray for *everyone* because of a few bad apples. So, if Amazon et al are eating your lunch, fight them... don't weaponize the ecosystem with a badly thought out "new" license type...
1 reply 0 retweets 0 likes
And as you are employed by Amazon consider the revenue loss - because this *will* trend and other cloud providers will eat your lunch. My bet is MSFT/Azure will set the tone here, not Amazon who are beyond the creepy line on this one IMHO. ( not directed at you - fwd to Bezos )
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.