veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

292
active users

#keyDB

0 posts0 participants0 posts today
Peter B.<p><span class="h-card" translate="no"><a href="https://mastodon.social/@reconditerose" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>reconditerose</span></a></span> I've just read you're maintainer of <a href="https://mastodon.social/tags/Valkey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Valkey</span></a> ? cool. 😎 </p><p>Didn't know about that (yet) either. I've considered <a href="https://mastodon.social/tags/KeyDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>KeyDB</span></a> as <a href="https://mastodon.social/tags/redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>redis</span></a> alternative due to using not-just-RAM.</p><p>Reading this at the moment, though:<br><a href="https://valkey.io/topics/persistence/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">valkey.io/topics/persistence/</span><span class="invisible"></span></a></p>
Scott Williams 🐧<p>The future of the multi-threaded <a href="https://mastodon.online/tags/redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>redis</span></a> alternative of <a href="https://mastodon.online/tags/KeyDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>KeyDB</span></a> seems uncertain now, with its core maintainer leaving Snap. <a href="https://mastodon.online/tags/Valkey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Valkey</span></a> is still going strong, though!</p><p><a href="https://github.com/Snapchat/KeyDB/issues/895" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/Snapchat/KeyDB/issu</span><span class="invisible">es/895</span></a></p>
:projetstodon: Shalien<p>Bon, apparemment <a href="https://mastodon.projetretro.io/tags/keydb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>keydb</span></a> à décidé de planter tout le serveur. Pratique, simple . Ca va que j'ai accès à la prise.</p><p><a href="https://mastodon.projetretro.io/tags/mastoadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mastoadmin</span></a></p>
:projetstodon: Shalien<p>Résultat de la soirée <a href="https://mastodon.projetretro.io/tags/promox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>promox</span></a> / <a href="https://mastodon.projetretro.io/tags/container" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>container</span></a> ....</p><p>BAH PUTAIN J'AURAIS AIMER QU'ON M'APPRENNE A FAIRE DES CONTAINERS AVANT.</p><p>Ca consomme rien comparé aux VM, j'ai pu monter un <a href="https://mastodon.projetretro.io/tags/redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>redis</span></a> (<a href="https://mastodon.projetretro.io/tags/keydb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>keydb</span></a>) , un <a href="https://mastodon.projetretro.io/tags/postgresql" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>postgresql</span></a> et remonter mon instance <a href="https://mastodon.projetretro.io/tags/synapse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>synapse</span></a> (<a href="https://mastodon.projetretro.io/tags/matrix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>matrix</span></a>) et le proco tourne à ... bah 0% en effet. </p><p>J'ai envie de souffler très fort tellement j'aurais pu les choses autrement avant ...</p><p>Et tout ca avec <a href="https://mastodon.projetretro.io/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a>, <a href="https://mastodon.projetretro.io/tags/HTTPS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HTTPS</span></a> et tout</p>
Serge from Babka<p>This discussion on HN about why you may not need anything other than Postgres: <a href="https://news.ycombinator.com/item?id=42036303" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">news.ycombinator.com/item?id=4</span><span class="invisible">2036303</span></a></p><p>brings up a good question about Redis- one I've wondered myself: Are we using Redis the wrong way?</p><p>The main use of Redis is as a simple key/value store. The idea is that if we are doing a process such as a DB query, we can cache the result. This is essentially memoization, and I remember this being used way back with a program called memcached.</p><p>Redis is a highly optimized key/value store, but many people (myself included) use hosted Redis servers. This introduces a lot of overhead on reads.</p><p>Wouldn't we be better off moving the key/value pair server as close to the application as possible, and then relying on writes being distributes to all instances? At worst we might get old data, but if we're using the system for caching, that shouldn't matter much, and we can instead rely on eventual consistency.</p><p>I'm curious as to other's thoughts on this.</p><p><a href="https://babka.social/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Redis</span></a> <br><a href="https://babka.social/tags/KeyDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>KeyDB</span></a> <br><a href="https://babka.social/tags/SystemArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SystemArchitecture</span></a></p>
hobbsc<p>anyone have any opinions about <a href="https://social.sdf.org/tags/keydb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>keydb</span></a> and <a href="https://social.sdf.org/tags/valkey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>valkey</span></a>? i was about to start a project with the former when i learned about the latter. i really like <a href="https://social.sdf.org/tags/redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>redis</span></a> and am looking into replacements.</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@Elucidating" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>Elucidating</span></a></span> Again:<br>Check my <a href="https://infosec.space/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GitHub</span></a> contributions and see for yourself...</p><p>The <a href="https://infosec.space/tags/rugpull" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rugpull</span></a> by <a href="https://infosec.space/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Redis</span></a> is just <a href="https://www.youtube.com/watch?v=9kpZ1vdQJsE&amp;t=1504s" rel="nofollow noopener noreferrer" target="_blank">inexcuseable</a> and not only did <a href="https://infosec.space/tags/Snapchat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Snapchat</span></a> basically make a better <a href="https://infosec.space/tags/multithreaded" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>multithreaded</span></a> <a href="https://infosec.space/tags/fork" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>fork</span></a> under <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BSD</span></a> 3-Clause named <a href="https://infosec.space/tags/KeyDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>KeyDB</span></a> for <a href="https://github.com/Snapchat/KeyDB" rel="nofollow noopener noreferrer" target="_blank">quite some time</a> , but <a href="https://github.com/redis/redis/pull/13157#issuecomment-2011733104" rel="nofollow noopener noreferrer" target="_blank">several</a> <a href="https://github.com/redis/redis/pull/13157#issuecomment-2013741227" rel="nofollow noopener noreferrer" target="_blank">big</a> <a href="https://github.com/redis/redis/pull/13157#issuecomment-2014186987" rel="nofollow noopener noreferrer" target="_blank">constributors</a> seem <a href="https://github.com/redis/redis/pull/13157#issuecomment-2014709005" rel="nofollow noopener noreferrer" target="_blank">pissed</a>...</p><p>So far, I saw quite significant contributions from <a href="https://infosec.space/tags/Tencent" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Tencent</span></a> <a href="https://github.com/enjoy-binbin" rel="nofollow noopener noreferrer" target="_blank">*</a>, <a href="https://infosec.space/tags/AlibabaCloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AlibabaCloud</span></a> <a href="https://github.com/redis/redis/pull/13157#issuecomment-2014737480" rel="nofollow noopener noreferrer" target="_blank">*</a> <a href="https://infosec.space/tags/aws" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>aws</span></a> and <a href="https://infosec.space/tags/RedHat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RedHat</span></a> and I'm convinced their <a href="https://infosec.space/tags/CLO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CLO</span></a>'s are <em>pissed</em> since their staff worked on those projects because with the leave of original creator of Redis it was stated that <a href="http://antirez.com/news/120" rel="nofollow noopener noreferrer" target="_blank"><em>it will remain 3-Clause BSD</em></a>...</p><p>And I do expect Redis to get <a href="https://github.com/redis/redis/pull/13157#issuecomment-2014340803" rel="nofollow noopener noreferrer" target="_blank">their asses handed in court so hard</a> they'll have to file for <a href="https://infosec.space/tags/bankrupcy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>bankrupcy</span></a> like <a href="https://infosec.space/tags/SCO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SCO</span></a> before the dust has settled...</p><p>I mean, look at <a href="https://github.com/redis/redis/pull/13157" rel="nofollow noopener noreferrer" target="_blank">that dumpsterfire</a> and tell me with a straight face this is how <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FLOSS</span></a> should be done!</p>
Schenkl<p>So, dann mal damit angefangen alle <a href="https://chaos.social/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Redis</span></a> Server in der Firma mit <a href="https://chaos.social/tags/KeyDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>KeyDB</span></a> zu ersetzen.<br>Ist ohnehin wohl das bessere Produkt, wenn man deren Beschreibung glauben mag ;)</p><p><a href="https://docs.keydb.dev/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">docs.keydb.dev/</span><span class="invisible"></span></a></p>