nrw.social ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Wir sind eine freundliche Mastodon Instanz aus Nordrhein-Westfalen. Ob NRW'ler oder NRW-Sympathifanten, jeder ist hier willkommen.

Serverstatistik:

2,8 Tsd.
aktive Profile

#Redis

10 Beiträge9 Beteiligte0 Beiträge heute

#Arch is replacing #Redis with #Valkey.

The transition period will be of 14 days, at the end of which the Redis package will be moved to the AUR.

I said it already one year ago after Redis switched its license to a very restrictive SSPLv1: I don’t get it. And I said that little, if anything, would have changed, and that the Redis community would have just been splintered into a bunch of forks, while the great offenders (AWS and Azure in the first line) would have just switched their cloud offerings to the more permissive forks, still without feeling any duty to contribute back.

Fast forward one year, that’s exactly what happened.

AWS is already offering Valkey as a drop-in replacement for Redis in ElastiCache. Most of the distros have already switched to Valkey, or are considering to do so. The only loser so far has been Redis itself, which has lost community support, users, developers and funding.

Lesson learned: if you build a FOSS project, and you’re pissed by Amazon and Microsoft monetizing it without contributing back, opting for a strict open-source (but NOT free) license that forces any users of your product to also release the full source code of what they’ve built with your product (not only any modifications they’ve made to your product itself) is a bad idea.

I mean, I would love to live in a world where such a strategy actually helps, where the “free-as-in-beer” folks can be sensibilized about the cost of their freeloading and where you can nudge them to be less evil with a license that forces them to build more in the open. But the truth is that this world is quite far from that vision. If the cost of forking is perceived as lower than the cost of contributing back, then you can assume that folks will just fork whatever was there at the time of the license change.

https://archlinux.org/news/valkey-to-replace-redis-in-the-extra-repository/

archlinux.orgArch Linux - News: Valkey to replace Redis in the [extra] Repository
Fortgeführter Thread

An official statement from Arch on valkey and redis is now available:

"Valkey to replace Redis in the [extra] Repository"
archlinux.org/news/valkey-to-r

If you have #nextcloud running on Arch see the post above for the changes to run valkey instead of redis.

archlinux.orgArch Linux - News: Valkey to replace Redis in the [extra] Repository
#ArchLinux#Redis#Valkey
Fortgeführter Thread

Latest grievance: The #Quarkus Cache guide says `null` will be cached (negative caching) but this is in fact only supported by the default provider (using the great Caffeine library for in-memory cache) but *it is not supported* by any other provider, such as #Redis. 🙃

quarkus.io/guides/cache#negati
quarkus.io/extensions/io.quark
github.com/quarkusio/quarkus/i
github.com/quarkusio/quarkus/d

quarkus.ioApplication Data CachingQuarkus: Supersonic Subatomic Java

At this point I'm contemplating rewriting this small #Quarkus application in #SpringBoot.

Every step on the way I'm running into some unsupported things.

Latest frustration: The Quarkus #Redis extension (based on Vert.x Redis 4.x) doesn't support Amazon #IAM. This will be supported in version 5. 🙃

While at the same time there's an official example from #AWS for Lettuce (which #SpringData Redis is based on).

docs.aws.amazon.com/AmazonElas

docs.aws.amazon.comAuthenticating with IAM - Amazon ElastiCacheHow to authenticate with IAM.

Primär schreibe ich meine Anleitungen tatsächlich für mich. 🙈 Weil es mir häufig so geht, dass ich mir Dinge aus mehreren Anleitungen zusammenbastle und in ein paar Wochen oder Monaten nicht mehr weiß, wie ich das eigentlich gemacht habe.


Also schreibe ich mir für mich wichtige Dinge auf und nutze dazu meinen Blog.


Diesmal habe ich Redis für Friendica installiert und dazu eine Anleitung geschrieben, wer Interesse daran hat, darf gerne hier weiterlesen.


Link: blogzwo.me/friendica-performan…


#Friendica, #Redis, #Optimierung, #Linux, #Debian

Blog:Zwo.meFriendica-Performance mit Redis unter Debian 12 optimierenSchritt-für-Schritt-Anleitung zur Installation und Konfiguration von Redis-Server unter Debian 12 zur Optimierung der eigenen Friendica-Instanz.

Valkey 對 hash 資料結構的改善

在 Lobsters 上看到「A new hash table」這篇,講 Valkey 對 hash 資料結構的改善。 其中 Valkey 是 Redis 在捨棄 open source license 後興起的專案。這類拋棄 open source license 的專案中,有個關鍵的點是「原廠」與「社群」之間的貢獻比率。 如果整個專案都只有「原廠」的人在參與,那 fork 出來的版本就不會有太多前景了;反過來如果「社群」有提供不少貢獻,那 fork 出來的版本就有機會欣欣向榮。 Valkey 的這個 hash 的改善本身固然很重要 (因為 hash 算是很基礎的資料結構,有很多地方會用到),另外一方面,這代表了「社群」這邊的能量是存在的,就很值得期待了。 …

blog.gslin.org/archives/2025/0

Gea-Suan Lin's BLOG · Valkey 對 hash 資料結構的改善在 Lobsters 上看到「A new hash table」這篇,講 Valkey 對 hash 資料結構的改善。 其中 Valkey 是 Redis 在捨棄 open source license 後興起的專案。這類拋棄 open source license 的專案中,有個關鍵的點是「原廠」與「社群」之間的貢獻比率。 如果...
#algorithm#data#hash