引导性超模型环境(dev/uat/prod)偏好
我们即将从头开始开发。很可能这将是使用其托管服务部署在Oracle中的单个组织网络。采取这种选择的首选方法是什么?
- 单个网络具有多个dev/uat/prod的渠道 或
- 每个Dev/UAT/产品的孤立网络
可以理解,当地Docker部署等可以实现开发,但是为了保持一致,将其用于托管服务可能是一个好主意。
We are about to start development from scratch. Most likely this will be a single organisation network deployed in Oracle using their managed service. What is the preferred way to approach this?
- Single network with multiple channels for dev/uat/prod
OR - Isolated networks for each dev/uat/prod
It's understood that dev can be achieved by local docker deployment etc, but for consistency, it might be a good idea to get it going in the managed service, too.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
分离各种环境的最常用的最佳实践之一就是绝对使生产与所有其他环境不同。即使仅从安全角度来看。这可能会导致各种审核问题,您最终可能需要回答为什么您不分开生产。
另外,如果您预见到必须以自动方式进行部署过程,请考虑至少有一个环境来干燥此过程。
除此之外,鉴于HLF的设置方式,我认为这将是一种口味问题。
只是我的2美分。
Among the most commonly used best practices to separate the various environments is to definitely keep Production apart from all other environments. Even if only from a security perspective. It may cause all kinds of auditing questions you may eventually have to answer as to why you did NOT separate production.
Also, if you foresee you have to go through a deployment process in an automated fashion, consider having at least one environment to dry-run this process.
Other than that, given the way HLF is set up, I think it will be a matter of taste.
Just my 2 cents.