# MQTT vs Database Replication Architecture

**URL:** <https://forum.inductiveautomation.com/t/mqtt-vs-database-replication-architecture/112209>\
**Category:** Ignition\
**Created:** [November 15, 2025, 10:18pm UTC](https://forum.inductiveautomation.com/t/mqtt-vs-database-replication-architecture/112209 "2025-11-15T22:18:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eugene49](https://avatars.discourse-cdn.com/v4/letter/e/c6cbf5/32.png) [@Eugene49](https://forum.inductiveautomation.com/u/Eugene49)\
**Post date:** [November 15, 2025, 10:18pm UTC](https://forum.inductiveautomation.com/t/mqtt-vs-database-replication-architecture/112209/1 "2025-11-15T22:18:51Z")

</div>

Really, just a thought and thinking out loud.

If database replication were already a thing, and very mature.

Why do many of the architectures use MQTT to send data to cloud for analysis, why not use database to store data on site and replicate it to the cloud?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [November 15, 2025, 11:03pm UTC](https://forum.inductiveautomation.com/t/mqtt-vs-database-replication-architecture/112209/2 "2025-11-15T23:03:39Z")

</div>

Bandwidth, basically.

Database replication is more chatty than a purpose-designed change-of-state protocol like MQTT.

---

<div class="post-metadata">

**Author:** ![Eugene49](https://avatars.discourse-cdn.com/v4/letter/e/c6cbf5/32.png) [@Eugene49](https://forum.inductiveautomation.com/u/Eugene49)\
**Post date:** [November 18, 2025, 10:51pm UTC](https://forum.inductiveautomation.com/t/mqtt-vs-database-replication-architecture/112209/3 "2025-11-18T22:51:02Z")

</div>

Coincidentally, I was ask develop database replication using MQTT. That is check if there is any changes on the source table and send mqtt message.

Quick googling says I can use CDC, change data capture, of database.

Any thoughts?

– The truth to the matter:  
i was on the meeting, and said, Phil, mentioned we can save bandwidth using MQTT.  
Then say: “We use MQTT to replicate then.”  
– i hope this was a fact. pun intended.

---

<div class="post-metadata">

**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\
**Post date:** [November 18, 2025, 11:19pm UTC](https://forum.inductiveautomation.com/t/mqtt-vs-database-replication-architecture/112209/4 "2025-11-18T23:19:44Z")

</div>

> [@Eugene49](#):
>
> Coincidentally, I was ask develop database replication using MQTT. That is check if there is any changes on the source table and send mqtt message.

MQTT was invented for Data Centres to synchronise with each other. Its use case isn’t limited to Edge Nodes.

---

<div class="post-metadata">

**Author:** ![Eugene49](https://avatars.discourse-cdn.com/v4/letter/e/c6cbf5/32.png) [@Eugene49](https://forum.inductiveautomation.com/u/Eugene49)\
**Post date:** [November 18, 2025, 11:23pm UTC](https://forum.inductiveautomation.com/t/mqtt-vs-database-replication-architecture/112209/5 "2025-11-18T23:23:56Z")

</div>

Right, in the end, it all just data being sent anyway.  
I will look at database CDC, if this is an option.