简体   繁体   English

Amazon AWS RDS实例组织

[英]Amazon AWS RDS Instance organisation

I am migrating to Amazon Web Services. 我正在迁移到Amazon Web Services。 I have a production site and associated mySQL Database, and I also have a staging site to try out changes prior to pushing to production. 我有一个生产站点和关联的mySQL数据库,并且我还有一个登台站点,可以在进行生产之前尝试进行更改。

In terms of AWS RDS, how do I manage these two databases? 就AWS RDS而言,我该如何管理这两个数据库? Should they both exist in the same instance, or should they each have their own instance? 它们应该都存在于同一个实例中,还是应该各自具有自己的实例?

My staging site does not have to be continuously available, does this change which option is best suited? 我的暂存站点不必一直可用,此更改最适合哪个选项吗?

I think those databases should live in different instances. 我认为这些数据库应位于不同的实例中。 Production DB should definitely have its own instance. 生产数据库肯定应该有自己的实例。 There are many reasons to that: 原因有很多:

  1. What happens if you have a bug in staging and you spam your instance with CPU-eating queries? 如果您在登台过程中遇到错误,并且使用CPU占用的查询向实例发送垃圾邮件,会发生什么情况? If it is the same instance your production DB might be effected. 如果是同一实例,则可能会影响您的生产数据库。

  2. It is good to have instance monitoring only for production. 仅对生产进行实例监视是很好的。

  3. You will be able to set up configuration on the production instance that should not be set on staging such as multi-az availability. 您将能够在生产实例上设置不应在分段上设置的配置,例如多az可用性。

  4. You can stop the staging instance when ever you want and re-start it with just the data it had when you stopped it. 您可以随时停止分段实例,并仅使用停止实例时拥有的数据重新启动该实例。

All in all, no reason to mix the two into the same instance. 总而言之,没有理由将两者混入同一实例中。 One for production, one for staging. 一台用于生产,一台用于分期。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM