[hyperman1]

I simply try to document the as is architecture, and found out I can't really do it as I want.

As I see it, I have a lot of tiny items like servers, clusters, applications, database schemas, services, network things, ... all interlinked by relations. Relations are two way, and typically of the kind 'contains' or 'talks to'. The main problem: There are a lot of them, even if they are all tiny.

I'd love to have a good way to organize all this. wikis require too much clicking around. I'd love to ask questions like: What goes down if this subsystem disappears. So anyone willing to share experience is appreciated.

Now all this is simply about documenting what is. The AskHN wants to go a step further: How to document what should be.