# 为什么 Discourse 开始运行自己的 Redis 而不是使用 Elasticache？

**URL:** <https://meta.discourse.org/t/why-did-discourse-start-running-their-own-redis-instead-of-using-elasticache/107658>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [2019年一月27日 19:15 UTC](https://meta.discourse.org/t/why-did-discourse-start-running-their-own-redis-instead-of-using-elasticache/107658 "2019-01-27T19:15:27Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [2019年一月29日 09:51 UTC](https://meta.discourse.org/t/why-did-discourse-start-running-their-own-redis-instead-of-using-elasticache/107658/3 "2019-01-29T09:51:07Z")

</div>

Also … not to forget. This offers us significant cost savings.

When you use ElasticCache you pay for the instances **plus** a tax for the ElasticCache service. Additionally we get much better control on utilisation since we can run multiple redises if we wish on a single instance.

---

_[View the full topic](https://meta.discourse.org/t/why-did-discourse-start-running-their-own-redis-instead-of-using-elasticache/107658)._