Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Having a(n accurate) service graph of all your (internal and external) dependencies is a game changer in troubleshooting issues like this.


Do you need another dependency for that? A dependency to manage dependency hell.


Optimally, that’s already part of your observability stack, and might well be a built-in feature. In a certain scale/landscape it easily pays off.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: