Skip to content

Separating the backends #88

Description

@jwoertink

We have a few now.

  • Dev
  • Redis
  • Legacy Redis
  • Postgres (requested)
  • NATS (requested)
  • LavinMQ (reqeuested)

At this point, I think we should remove all backends from Cable, then make them each a separate shard. You include cable and the backend you want with it. Then other people could create new backends later. To do this, I think there's a few bits in #79 that could be abstracted out first.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions