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
  • #55

Closed
Open
Created Jun 27, 2024 by Dan Jones@danjonOwner

Managing multiple projects using a shared backbone

What happens if you have 2 concurrent projects using the same backbone to manage different concurrent campaigns

Issues:

  • separating subscriptions
    • who receives what?
    • how do you avoid receiving lots of noise?
  • managing permissions
    • who is allowed to control which resources?
    • who manages the permissions?
    • who enforces the permissions?
  • is the design fundamentally different if we switch from ephemeral to permanent infra?
  • how do you handle the backbone relay concept?
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking