#Redis

Valkey to replace Redis in the [extra] Repository

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

#ArchLinux #Redis #Valkey #Linux

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. 🙃

https://quarkus.io/guides/cache#negative-cache
https://quarkus.io/extensions/io.quarkus/quarkus-redis-cache/
https://github.com/quarkusio/quarkus/issues/39547
https://github.com/quarkusio/quarkus/discussions/42940

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. 🙃

https://quarkus.io/guides/cache#negative-cache
https://quarkus.io/extensions/io.quarkus/quarkus-redis-cache/
https://github.com/quarkusio/quarkus/issues/39547
https://github.com/quarkusio/quarkus/discussions/42940

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).

https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/auth-iam.html

✅ Done: Migration from #Redis to #Redict for caches
⏳ In Progress: Migration from MariaDB to Galera Cluster

We were still struggling with email delivery from Forgejo. It looks like some queues are corrupted and restoring them is very hard. Most queued messages are spam or registration emails with already expired tokens. Finally, we made the decision to reset the queue and will do that in a few minutes.

We are using the opportunity to switch the queues to #redict / #redis, which was a planned project anyway (a requirement for clustering our Forgejo to multiple instances).

【図解解説/初心者OK】Next.jsとHonoで爆速タイピングゲームを作ろう【Redis/Bun/TypeScript/Upstash/TailwindCSS】
https://qiita.com/Sicut_study/items/c12faaf962646bee34f7?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #Redis #TypeScript #Next_js #Hono

Can you have a #Pixelfed and #Mastodon in the same server?

I'm seeing very weird things.

1. Some Mastodon lists have 0 posts right now, refreshed and gone.

2. Following a Pixelfed user from Mastodon seems to have no effect.

All systems in Pixelfed and Mastodon seem up.

Could there be a conflict with #Redis or similar?

#MastoAdmin

Redis + Ratatui = 🔥

🧰 **ratisui**: A TUI for exploring Redis databases from the terminal!

🚀 Supports command execution, auto completion, logging & more!

🦀 Written in Rust & built with @ratatui_rs

⭐ GitHub: https://github.com/honhimW/ratisui

#rustlang #ratatui #tui #redis #database #terminal #explore #tool #commandline

The corporation behind #Redis is now starting to chase #OpenSource client libraries claiming trademark violations https://github.com/redis-rs/redis-rs/issues/1419 and are attempting to have the projects transferred to them.

If it wasn't obvious before, now is a good time to fuck the hell off from that software. Just use #Valkey or one of the other alternatives.

#Redis : Destroys their reputation with a shady license change

Community: Moves to #Valkey fork

Redis: It is the people that are wrong, we'll use trademark to control the ecosystem

Result:

https://github.com/redis-rs/redis-rs/issues/1419

#rust #rustlang

Rearchitecting: #Redis to #SQLite
https://wafris.org/blog/rearchitecting-for-sqlite

Wafris' migrated from #Redis to #SQLite for its Rails middleware client. SQLite outperformed Redis in its specific use case, offering about 3x speed improvement locally.

https://wafris.org/blog/rearchitecting-for-sqlite

#Hollo now can work without #Redis. It uses Redis as a cache and queue backend if the REDIS_URL environment variable is provided, but if not given, it caches in memory and works without a queue. This is an option to consider if you have a few following/followers.

I've migrated Redis to KeyDB and separated the volatile cache from Sidekiq jobs and Mastodon timelines. While this might not result in a performance boost due to the low load, it will enable some exciting new features (spoiler: KeyDB supports master-master replication).

Stay tuned!

#Redis #KeyDB #Mastodon #Sidekiq #BSDCafe #BSDCafeServices #BSDCafeUpdates

Sentry is hiring Senior Software Engineer, Platform

🔧 #golang #python #rust #django #kafka #postgresql #redis #seniorengineer
🌎 Toronto, Canada
⏰ Full-time
🏢 Sentry

Job details https://jobsfordevelopers.com/jobs/senior-software-engineer-platform-at-sentry-io-feb-22-2024-9c4dd4?utm_source=mastodon.world&utm_medium=social&utm_campaign=posting
#jobalert #jobsearch #hiring

#Fedify has supported optional queuing for outgoing activities, with two built-in message queue backends: InProcessMessageQueue, which is suitable for development, and DenoKvMessageQueue, which is only available in Deno.

Fedify has also had two built-in cache backends, MemoryKvStore, which is suitable for development, and DenoKvStore, which is only available in Deno.

Now, however, by installing the @fedify/redis package, you can use #Redis as both a message queue backend and a cache backend! Unlike DenoKvMessageQueue and DenoKvStore, it's also available for #Node.js and #Bun.

This feature was made possible with the support of @ghost.

https://github.com/dahlia/fedify-redis

#fedidev