分段数据库困境 [英] Staging database predicament

问题描述

假设

• 生产


• 暂存


• Dev

据我所知，Staging数据库需要与生产数据库同步
但是，

As far as I know, Staging database need to be in sync with Production database But,

当我们开发时，我们可以使用 Dev 数据库并更改模式来做任何我们想要的操作。
现在来看鸡肉& Egg问题。

When we are developing, we can do whatever we want with Dev database and change schema. Now here comes the Chicken & Egg problem.

要在Staging中测试，暂存数据库模式需要根据Dev数据库中所做的更改进行更改。但是，Staging数据库需要与Production同步。

To test in Staging, Staging database schema need to be changed according to changes made in Dev database. But the Staging database need to be in sync with Production.

你们如何解决这个问题？

How do you guys get around this problem?

推荐答案

分段需要与生产同步，直到您部署新的更改。

Staging needs to be in sync with production, only up to the point where you are deploying new changes.

那就是创建一个名为Test的第四个环境，验证新的升级。我们称之为UAT / Test，它通常是Staging服务器上的第二个数据库。

That or make a 4th environment called Test where new upgrades are validated. We call ours UAT/Test, and it is typically a second database on the Staging server.

精确的方法将取决于你如何保持同步。你实际上是否使用复制？或者只是Prod到Stage的备份/恢复？

Exact methodology will depend on how you are keeping things in sync. Are you actually using replication? Or just a backup/restore of Prod to Stage?

这篇关于分段数据库困境的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！