# Mantenere il discorso su un sistema di archiviazione chiave-valore open-source

**URL:** <https://meta.discourse.org/t/keeping-discourse-on-an-open-source-key-value-storage-system/303669>\
**Category:** Development\
**Created:** [13 Aprile 2024, 1:17pm UTC](https://meta.discourse.org/t/keeping-discourse-on-an-open-source-key-value-storage-system/303669 "2024-04-13T13:17:04Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![mcdanlj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcdanlj/32/131829_2.png) [@mcdanlj](https://meta.discourse.org/u/mcdanlj)\
**Post date:** [7 Settembre 2024, 2:22am UTC](https://meta.discourse.org/t/keeping-discourse-on-an-open-source-key-value-storage-system/303669/5 "2024-09-07T02:22:30Z")

</div>

Valkey sta ottenendo miglioramenti in termini di [prestazioni](https://valkey.io/blog/unlock-one-million-rps/) e [impronta di memoria](https://valkey.io/blog/valkey-memory-efficiency-8-0/). L’[imminente Valkey 8](https://valkey.io/blog/valkey-8-0-0-rc1/) sembra incredibile.

Mi sembra chiaro a questo punto che “Redis” sia il fork proprietario e “Valkey” sia la linea principale. Dall’esterno sembra che il fork abbia effettivamente accelerato il lavoro in Valkey.

---

_[View the full topic](https://meta.discourse.org/t/keeping-discourse-on-an-open-source-key-value-storage-system/303669)._