I am developing a simple microservice that has a cyclical nature:
- waits until someone pubblish a message on an MQTT topic
- performs actions
- sends a reply and then waits for the next message
I need to share with others all the steps of creating this microservice. I was thinking of using an activity diagram but all the examples I found don't seem to cover this type of behavior.
What is the more appropriate UML diagram to describe cyclic operation and why?
One thing to keep in mind is that there is no command to stop receiving messages, it starts receiving as soon as it is started and stops only when it is terminated.
