Otto should rather be compared to LocalBroadcastManager. This is because the both Otto and LocalBroadcastManager do not support inter-process communication.
Otto's pros:
- Much less code and more readable code.
- Complex objects can be passed through (no object serialization is required).
- Instant value callback via
@Producer
s.
Otto's cons:
- Otto uses reflection, that is why it might be slower than LocalBroadcastManager if you, for instance, send integer values very frequently.