Application B has multiple datasets that it shares with other apps. One dataset goes to Application A to be enhances and passed on to Application 2 which is a data lake.
Application B has another dataset that it feeds right into the data lake (Application 2) that Application 1 needs.
If Application B goes down, Application A and Application 2 will be notified but Application 1 will not. Application 2 is a data lake so it doesn't matter to them; the data lake is still fully functional, it's just missing some data from B. 1's relationship to 2 is not impacted. Is the only way to show that impact is to have a L1 relationship between B & 1? What if the data that is impacted from B is only the data that is going into A and we did build that L1 relationship between B & 1?
Do we need to be more granular and show relationships at the service level (only)? Do we need to be even more granular and show relationships at the microservice level (only)?
We have all of the applications so we can show the B2B at that level but we run into the initial problem I demonstrated. We also have all of the microservices and could potentially handle it at this level also but that seems like a lot. We would definitely have to program the building of relationships, possibly using tags if this is supported OOB but scripting B2B relationships via cloud tags/labels shouldn't be too hard but severing those relationships automatically could be problematic.
Are there OOB solutions for this?
