# Building an Amazon Discourse pilot, planning for scale

**URL:** <https://meta.discourse.org/t/building-an-amazon-discourse-pilot-planning-for-scale/45458>\
**Category:** Self-hosting\
**Created:** [Junho 9, 2016, 3:59am UTC](https://meta.discourse.org/t/building-an-amazon-discourse-pilot-planning-for-scale/45458 "2016-06-09T03:59:22Z")\
**Posts on this page:** 1\
**Showing post:** 11

<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:** [Junho 14, 2016, 10:40pm UTC](https://meta.discourse.org/t/building-an-amazon-discourse-pilot-planning-for-scale/45458/11 "2016-06-14T22:40:16Z")

</div>

> [@edanto](#):
>
> would anyone be able to point me to a resource that describes how to build/install discourse to plan for scale

I’m not aware of anything Discourse-specific, but there’s hundreds or thousands of opinions “out there” about how to scale Rails, PostgreSQL, and Redis, and Discourse is a fairly standard Rails/PostgreSQL/Redis application. As the person who is primarily responsible for the infrastructure here at CDCK, I’ve got to say that my job pretty much _never_ involves worrying about scaling an individual site; my time is spent working on the problems of automation and scaling for the entire customer base. Rails+PgSQL+Redis just chugs along nicely all by itself.

---

_[View the full topic](https://meta.discourse.org/t/building-an-amazon-discourse-pilot-planning-for-scale/45458)._