# Discourse synchronisation for multiple instances

**URL:** <https://meta.discourse.org/t/discourse-synchronisation-for-multiple-instances/138227>\
**Category:** Development\
**Created:** [January 10, 2020, 9:25am UTC](https://meta.discourse.org/t/discourse-synchronisation-for-multiple-instances/138227 "2020-01-10T09:25:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [January 10, 2020, 11:08am UTC](https://meta.discourse.org/t/discourse-synchronisation-for-multiple-instances/138227/2 "2020-01-10T11:08:12Z")

</div>

Discourse is not designed for an application like this. It is extremely unlikely you will be able to get two-way postgres synchronisation working in a way that doesn’t break Discourse.

> [@Surendra-Patil](#):
>
> I am thinking to try changing auto-increment sequence of every table to UUID in database.

Changing this would require some significant changes in the Discourse code.

> [@Surendra-Patil](#):
>
> Slave instance can be online/offline but will be used by users. But whenever an offline instance comes online it should be able to sync with master server without creating conflicts and all update all the latest data.

If you make the slaves read-only, and synchronise postgres one-way, then it might be possible to make this work… but it will be difficult

---

_[View the full topic](https://meta.discourse.org/t/discourse-synchronisation-for-multiple-instances/138227)._