# Discourse High Availability

**URL:** https://meta.discourse.org/t/discourse-high-availability/55091
**Category:** Self-hosting
**Created:** [January 3, 2017, 7:58am UTC](https://meta.discourse.org/t/discourse-high-availability/55091 "2017-01-03T07:58:36Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Assma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/assma/32/473827_2.png) [@Assma](https://meta.discourse.org/u/Assma)
#### Post date: [December 18, 2024, 10:27pm UTC](https://meta.discourse.org/t/discourse-high-availability/55091/5 "2024-12-18T22:27:16Z")

</div>

I couldn’t find close answers elsewhere.  
I understood that Standalone installation of Discourse is recommended for its simplicity and robustness in standard environments. However, to provide High Availability, ones are suggesting bursting standalone mode into multiple containers ([29413](https://meta.discourse.org/t/move-from-standalone-container-to-separate-web-and-data-containers/29413)), others redesign fully separate deployments.

1. Question1: Since HA is about duplicating services (web and db) with reliable failover, does Discourse propose such solution where both web-services and DBs are replicated inside containers?
2. Question2: For web-services, a load-balancer would be needed to ensure charges equity between instances. What are Discourse experts and community recommendations?
3. Question3: For containerised-DB HA, what is the most preferable way to manage postgreSQL replication?
4. Question4: Same question for Redis.

---

_[View the full topic](https://meta.discourse.org/t/discourse-high-availability/55091)._