# Cluster Templates Support \[High Availability\] \[Redundancy\]

**URL:** https://meta.discourse.org/t/cluster-templates-support-high-availability-redundancy/179308
**Category:** Feature
**Created:** [February 11, 2021, 8:46am UTC](https://meta.discourse.org/t/cluster-templates-support-high-availability-redundancy/179308 "2021-02-11T08:46:03Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![dadberg](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dadberg/32/208954_2.png) [@dadberg](https://meta.discourse.org/u/dadberg)
#### Post date: [February 11, 2021, 8:46am UTC](https://meta.discourse.org/t/cluster-templates-support-high-availability-redundancy/179308/1 "2021-02-11T08:46:03Z")

</div>

I propose these additions to the templates folder:

- postgres.master.yml
- postgres.slave.yml
- redis.master.yml
- redis.slave.yml

This way, Discourse clustering, and all the agony around this subject will vanish.

As per my understanding, Redis container cannot be duplicated due to message-bus unique transactions, but apparently it can be replicated.

**Architectural Benefits?**

1. Ability to bootsrap (web.template.yml + web.template.yml + redis.master.yml) within the master node and only (web.template.yml + postgres.slave.yml + redis.slave.yml) within the slave node **WITHOUT** referring back to the master node which offloads the pressure significantly and leverages the power of Nginx load balancer in front of them all.

2. The ambitious support for a UI clustering section within the admin dashboard will turn achievable!

Discourse is arguably the most advanced open source application ever created, thanks for the team behind this state of the art.

---

<div class="post-metadata">

### Author: ![mcdanlj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcdanlj/32/131829_2.png) [@mcdanlj](https://meta.discourse.org/u/mcdanlj)
#### Post date: [June 6, 2021, 4:13pm UTC](https://meta.discourse.org/t/cluster-templates-support-high-availability-redundancy/179308/3 "2021-06-06T16:13:10Z")

</div>

This would be useful for streaming backup even if no HA failover is configured. Have you created a PR with suggested contents for such files?

How would you expect to manage database updates to new major postgres versions when deploying across multiple nodes in this fashion?
