doc: zbus: improve suggested uses
Developers may be uncertain about which observer type to use in zbus,
potentially resulting in improper subsystem use. Fix that by adding an
explicit differentiation between the observer's type in the `Suggested
uses` section.
Fixes #58004
Signed-off-by: Rodrigo Peixoto <rodrigopex@gmail.com>
diff --git a/doc/services/zbus/index.rst b/doc/services/zbus/index.rst
index b44035c..c066d4d 100644
--- a/doc/services/zbus/index.rst
+++ b/doc/services/zbus/index.rst
@@ -475,7 +475,7 @@
Suggested Uses
**************
-Use zbus to transfer data (messages) between threads in one-to-one, one-to-many, and many-to-many synchronously or asynchronously.
+Use zbus to transfer data (messages) between threads in one-to-one, one-to-many, and many-to-many synchronously or asynchronously. Choosing the proper observer type is crucial. Use subscribers for scenarios that can tolerate message losses and duplications; when they cannot, use listeners. In addition to the listener, another asynchronous message processing mechanism (like :ref:`message queues <message_queues_v2>`) may be necessary to retain the pending message until it gets processed.
.. note::
Zbus can be used to transfer streams from the producer to the consumer. However, this can increase zbus' communication latency. So maybe consider a Pipe a good alternative for this communication topology.
