antirez / antirez/disque

Project status update!

Offen
#213 7 Kommentare 54 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
C
Sterne
8.1k
Forks
532
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

Hi all,

many of you ask what will happen with Disque. Here is all the news:

1. The project is in the process of being translated to a Redis module. The code duplication with Redis was *impossible* to handle. I tried and I failed. So that was the plan.
2. I'm sitting in an alpha code base of Disque as a module of Redis that does not even compile but is a very good start... I translated most data structures in the past few months, but more importantly as a side effect I added to Redis modules all the APIs I needed (Cluster API and Timer API). I think I need yet another API to force replication out of context... but I'm not 100% sure.
3. Disque module will be released **under the AGPL license**, not BSD as Redis core.
4. Redis 6 **will not be released if we don't have an RC version of Disque** at least.
5. ETA: You should see Disque in beta version before the end of the year. RC in 6 months.
6. The new Disque should be mostly API compatible with the old one, and will have exactly the same guarantees. Will be AP, federated, and so forth. Same stuff. Just as a module.
7. It will live in a different repository compared to Redis. Very probably this same repository: at some point I'll force-push the new project, and leave the current implementation as a branch for historical reasons.

If you have questions I'm here.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.