Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
communications-backbone communications-backbone
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 25
    • Issues 25
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Communications Backbone System
  • communications-backbonecommunications-backbone
  • Issues
  • #44

Closed
Open
Created Mar 23, 2023 by Dan Jones@danjonOwner

Replace shared RMQ container instance with RMQ container per instance

At present we have multiple backbones sharing a common rabbitmq instance. This poses a bumber of problems with uniqueness and separation:

  • A partner of the SPINE project can subscribe to # and receive messages across all projects.
  • If you create 2 clients with the same ID in 2 separate backbone instances, as it stands they will share the same queues.
  • You can't have a test instance for a project with the same set of clients.

It may be possible to solve this in code with things like rabbit namespaces but given we want the backbone to be ephemeral infra it probably makes sense to just use separate rmq instances and ring-fence everything.

Edited Mar 27, 2023 by Dan Jones
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking