在 DynamoDB 上管理开发/登台/生产? [英] Managing dev/staging/production on DynamoDB?

问题描述

我们开始使用 DynamoDB，并希望为开发/登台/生产提供单独的环境.我们想不出一个自然的方法来做到这一点——我们只是创建单独的 AWS 账户吗?还是我们使用相同的帐户，但在我们的表中添加愚蠢的前缀(dev-products"、staging-products"、prod-products")?

We're starting to use DynamoDB, and want separate environments for dev/staging/production. We can't figure out a natural way to do this---do we just create separate AWS accounts? Or do we use the same account, but add silly prefixes to our tables ("dev-products", "staging-products", "prod-products")?

推荐答案

使用任何亚马逊产品管理此问题的标准方法是创建单独的帐户，然后使用合并计费，这样就不会使计费方面复杂化.我喜欢这个的一点是，您不会冒着意外运行错误命令而破坏生产代码的风险.显然，如果您登录到错误的实例，它对您没有帮助，但它仍然有很大帮助.

The standard way to manage this with any amazon products is to create separate accounts and then use consolidated billing so that it doesn't complicate the billing aspect. The thing i like about this is that you don't risk breaking the production code by accidentally running the wrong command. Obviously it doesn't help you if you're logged into the wrong instance but it still helps quite a bit.

多个帐户的其他用途可能是管理权限和更好的测试.将帐户分开有助于测试，因为您可以 100% 复制生产帐户，并在需要测试新功能时打开和关闭它.我已经与亚马逊高级支持人员讨论过这个问题，他们说这似乎是大公司的标准做法.一些较大的公司有很多账户.在我的工作中，我们只有 3 个，我发现它每天都更有用.

Other uses for multiple accounts could be to manage permissions and better testing. Having the accounts separate helps testing because you can reproduce the production account 100% and turn it on and off when you need to test new features. I've talked with amazon premium support about this issue and they've said that this seems to be standard practice for the larger companies. Some of the larger companies have many accounts. At my work here we just have 3 and I find it more useful every day.

这篇关于在 DynamoDB 上管理开发/登台/生产?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！