# Performance, Scaling, and HA requirements

**URL:** <https://meta.discourse.org/t/performance-scaling-and-ha-requirements/60098>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [29 Marzo, 2017 12:49 UTC](https://meta.discourse.org/t/performance-scaling-and-ha-requirements/60098 "2017-03-29T12:49:45Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [29 Marzo, 2017 22:42 UTC](https://meta.discourse.org/t/performance-scaling-and-ha-requirements/60098/3 "2017-03-29T22:42:09Z")

</div>

Given the highly variable (but, I assume, predictable) load spikes, an elastic service like AWS will _probably_ be your best bet; you can chuck more app servers into the pool during load spikes to keep things going. There’s nothing special about Discourse from a scaling and HA perspective, it’s just a regular ol’ Docker-enabled Rails application with PostgreSQL and Redis; any guide out there dealing with scaling those technologies will give you what you need to know to make Discourse do well. That’s not to say it’s _easy_; reliably scaling any technology in the face of large load spikes takes a fair chunk of work, but there’s nothing Discourse-specific in there.

---

_[View the full topic](https://meta.discourse.org/t/performance-scaling-and-ha-requirements/60098)._