Something went wrong while setting issue due date.
Managing multiple projects using a shared backbone
Open
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?
The first word of the publish topic is intended to be the project. If we enable clients with multiple subscriptions then we can have different project prefixes on the topics.
Then you still probably want a permissions layer that says which projects a given client is allowed to make a subscription to. That also means the backbone needs to be aware of the current projects and project history.
Would that require an active state (like a db) or just config-as-code that's loaded on startup and re-read on change.
Please register or sign in to reply