You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We really like the relationships between components (dependancy) feature in compass. As an organization working with event driven architecture I feel there could be an opportunity to extend the dependency capability to be more flexible.
For example in event driven architecture we tend to care less about the dependent services and more about the events a service subscribes or emits... This is perhaps different to dependency but shares similarities.
E.g.
Service A
Emits: CustomerRegistered
Service B:
Subscribes: CustomerRegistered
Emits: CustomerNotificationCreated
Service
Subscribes: CustomerRegistered
Emits: CustomerPreferencesCreated
This is really crude, but something like this, would allow a really useful way to understand how events progress between systems.
relationships:
SUBSCRIBES:
- CustomerRegistered
EMITS:
- CustomerPreferencesCreated
DEPENDS_ON:
- 'ari:cloud:compass:00000000-0000-0000-0000-000000000000:component/00000000-0000-0000-0000-000000000000/00000000-0000-0000-0000-000000000000'
- 'ari:cloud:compass:00000000-0000-0000-0000-000000000000:component/11111111-0000-0000-0000-000000000000/00000000-0000-0000-0000-000000000000'
This type of feature is available in other platforms and I think something like this would be welcomed by the event driven community.
Would love to hear what other people think.
Keep up the great work!