Re: [mqtt] Sync data between web server

[Sumeet Puri]

Hi Vikas, 

It really depends on the message exchange patterns. What a broker gives you is the ability to decouple the multiple servers from each other. You publish to the broker and whoever is interested subscribe to that data. So if the same data has to go to multiple servers, the publisher only needs to write once, and the consumers can all get a copy of the data. With MQTT (and AMQP) topic based filtering is also possible. 

If you go for persistence, then the consuming web servers can also be offline, and the broker will store the data for them to be available.

Point to point communication is almost always going to fall short, even if you can live with it today. A broker based architecture proves simpler in most cases, for example, it will allow you to have new producers and consumers added in, without any changes to the current ones, such as analytics.

You need to think about throughput, slow consumers causing an impact on publishers and other consumers, burst handling, high availability, disaster recovery, multi-site, filtering, latency, fanout etc before you make a choice of the broker - there are many options available out there. 

Thanks and Regards, 

Sumeet. 

On 31 Mar 2017, at 10:21 AM, Vikas Prasad <vikas....@gmail.com> wrote:

Hi,

I am new to MQTT protocol. I need to design a system where in multiple servers (less than 10) can share and sync data among themselves.

No client will be involved in the sync process.

For this kind of design, do i need to have broker created or web server itself can communicate among themselves?

--
To learn more about MQTT please visit http://mqtt.org
---
You received this message because you are subscribed to the Google Groups "MQTT" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mqtt+uns...@googlegroups.com.
To post to this group, send email to mq...@googlegroups.com.
Visit this group at https://groups.google.com/group/mqtt.
For more options, visit https://groups.google.com/d/optout.