n层架构的管理和部署

发布于 2024-07-08 02:49:49 字数 96 浏览 8 评论 0原文

如何管理由具有混合依赖关系的多个网站、桌面应用程序、Web 服务和数据库组成的 n 层系统的开发和部署?

假设您有一个具有源代码控制和自动构建的持续集成环境。

How do you manage development and deployment of a n-tier system that's made up of multiple websites, desktop applications, web services and databases that have a mix of dependencies?

Assume that you have a continuous integration environment with source control and automated builds.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

紫轩蝶泪 2024-07-15 02:49:49

这是你会发现很难实现的事情。 然而,我们做的一件事是确保系统的每个不同部分都进行适当的健全性检查,例如您的数据访问层将执行以下操作:

public void OnStart(){
    if(database.SchemaVersion != this.RequiredDatabaseSchemaVersion)
        throw new DependencyException("The database was not the required version");
}

这个示例完全微不足道,但您应该明白这一点。

您可以做的另一件事是确保在打包应用程序时将其打包为一个单元。 因此,有人可以这样做:

MyApplication_v1234.msi /install web_app
MyApplication_v1234.msi /install web_services

显然,这取决于您计划如何分发应用程序。

希望这能给您带来一些思考。

This is something you'll find hard to achieve. However, one thing we do is to make sure that each distinct part of your system does the appropriate sanity checks, for example your data access layer will do something like:

public void OnStart(){
    if(database.SchemaVersion != this.RequiredDatabaseSchemaVersion)
        throw new DependencyException("The database was not the required version");
}

This example is totally trivial, but you should get the idea.

Another thing you can do is make sure that when you package your app you package it as one unit. So someone can do something like:

MyApplication_v1234.msi /install web_app
MyApplication_v1234.msi /install web_services

Obviously this depends on how you plan to distribute your app.

Hopefully this gives you something to think about.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文