I'm eager to learn about best practices in the microservices world concerning documenting the behavioural architecture of the whole.
To document microservice behaviour, and have discussions about it, we've come up with our own graphical schema. It's interesting, and useful and can be automated. But, now comes the tricky part: how do you document the complexities, interdependencies and all between microservices given different user stories? How do you pass on that knowledge to another? I know documentation might be a poor choice there, so how do you do it?
I'm sure we can think of our own solutions again, but this time I'd thought it be wise to ask for field-experience first. Thanks for sharing!
j
stuff ;)
I use gliffy.com and a normal wiki page
it is quite hard to write a multidimensional explorative documentation I think the best representation are multidimensional graphs :) so you can go through all levels and relations between the systems.
personally for documentation I don't care about user stories ... they are 1 paradigm to formulate a given scenario and the wanted output. :)
but in theory you can link them as well.
That's how I do it :)