WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Project status update! #213

@antirez

Description

@antirez

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions