API´s often are used for bidirectional communication.
We should mention that there are other ways to establish a communication if you have more than two participants. A prominent protocol is the MQTT-protocol, that uses a broker as a connect point. Applications can subscribe to a certain topic to get informed about changes. We call this a pub-sub-pattern that allows communication between a large number of participants.
One big advantage of pub/sub-patterns is an additional layer of security. A participant only knows the broker, but does not need direct access to the sender.
Thank you for bringing up the MQTT protocol! I think it's a great idea to write a separate blog post about it, especially since the version 5 release has added some really interesting features beyond the publish/subscribe model.
I hope you will find the blog worth reading. Once again, thank you for your input!
API´s often are used for bidirectional communication.
We should mention that there are other ways to establish a communication if you have more than two participants. A prominent protocol is the MQTT-protocol, that uses a broker as a connect point. Applications can subscribe to a certain topic to get informed about changes. We call this a pub-sub-pattern that allows communication between a large number of participants.
One big advantage of pub/sub-patterns is an additional layer of security. A participant only knows the broker, but does not need direct access to the sender.
Thank you for bringing up the MQTT protocol! I think it's a great idea to write a separate blog post about it, especially since the version 5 release has added some really interesting features beyond the publish/subscribe model.
I hope you will find the blog worth reading. Once again, thank you for your input!
Brilliant Idea, I definitively would like to read this.
Thanks !! added it to my list