An imaginary diagram of interactions between a large number of microservices isn't too different to a low-code representation of a software program. The ways i

An imaginary diagram of interactions between a large number of microservices isn't too different to a low-code representation of a software program. The ways in which endpoints interact and receive webhooks are like function calls with arguments and callbacks. Documentation for programs is tricky, but often it makes sense to embed the documentation alongside the code (docstrings, comments, etc). And where possible, it's nice for programs to be self-explanatory (minimizing the amount of documentation required in the first place). That can often require careful choice (and rectification) of variable, function, file and directory names and structure. I'm not sure if that'll help much in practice - perhaps it's an unrealistic comparison to make between microservice architectures and programs. But maybe it'll provide a few ideas.