From 8dff26a8b111e89e7b37c694ed3a194d1d9cd4d1 Mon Sep 17 00:00:00 2001 From: Lauri Ojansivu Date: Thu, 15 Feb 2018 16:38:38 +0200 Subject: [PATCH] Updated AWS (markdown) --- AWS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AWS.md b/AWS.md index 9bdfbf5..114a8f8 100644 --- a/AWS.md +++ b/AWS.md @@ -7,7 +7,7 @@ This setup runs very well for thousands of users. To improve scalability even more, add [Redis Oplog support](https://github.com/cult-of-coders/redis-oplog), also see related [Redis Oplog discussion forum post](https://forums.meteor.com/t/meteor-scaling-redis-oplog-status-prod-ready/30855/479). At AWS you can use AWS ElastiCache that has Redis support. -If there is other ideas to improve scalability, add info to [existing scalability issue](https://github.com/wekan/wekan-mongodb/issues/2) or [scalability forum post](https://discourse.wekan.io/t/cpu-utilization-problems-with-large-userbase/579/15) , there is also mentioned that smart-disconnect is already in Wekan. +If there is other ideas to improve scalability, add info to [existing scalability issue](https://github.com/wekan/wekan-mongodb/issues/2) or [scalability forum post](https://discourse.wekan.io/t/cpu-utilization-problems-with-large-userbase/579/15), there is also mentioned that smart-disconnect is already in Wekan. For Enterprises using Wekan xet7 recommends participating in Wekan development, see [Benefits of contributing your features to Upstream Wekan](https://blog.wekan.team/2018/02/benefits-of-contributing-your-features-to-upstream-wekan/index.html), having your own developers working on Wekan daily, and using Commercial Support at https://wekan.team , as Wekan Team [already has access to high performance bare metal servers at CNCF / Packet for running high load testing](https://blog.wekan.team/2018/01/wekan-progress-on-x64-and-arm/index.html). With the benefits you get by using Wekan, it’s [time well spent](https://blog.wekan.team/2018/02/time-well-spent/index.html).