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
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.
Component dependencies are a core concept of distributed architectures, and I really like how Compass natively supports component dependencies so that other features can be build atop the resulting dependency graph (e.g. announcements, as further discussed in Notifications for announcements).
I'm struggling a bit how to model external dependencies though, i.e. those that are not the engineering output of your own teams?
As an example, we (Utoolity) are building AWS integrations for the Atlassian platform, which requires us to closely track the API/SPI/SDK evolution of two major platforms, besides all the usual software dependencies on external libraries for an app's business logic etc.:
So while 2 strongly suggests that each team needs to curate their tailored stream of changes anyway, I'm finding myself right in the middle between the Compass dependencies and announcements capabilities and am curious about your thoughts in this regard?