Azure功能应用程序的Visual Studio中的清洁体系结构

发布于 2025-01-24 01:58:06 字数 874 浏览 2 评论 0原文

我需要为数据转换项目构建几个Azure功能应用程序。因此,很少有服务(我们需要作为单独的功能应用程序来应用可伸缩性)消耗或分享共同的宇宙DB,事件网格,服务总线等。

因此,对于设计,我正在关注 jason taylors干净的体系结构

这样的结构就是这样,

Solution
|
---src (Directory)
     |
     --- Domain Layer (Project)
     --- Application Layer (Project)
     --- Infrastructure Layer (Project)
     --- functions
       |
       --- Function1 (project)
       --- Function2 (project)
       --- Function3 (project)
     --- Web Ui (Project)

因此每个函数项目和UI都取决于应用程序层。

但是我担心的是,每当发生域层发生变化时,我们也需要部署所有功能,不是吗?

还是有最好的方法来处理这种情况?就像当主层更改时无需部署UI或功能吗?我已经听到了一些人工制品的方式..但尚不清楚。

I have a requirement of building few azure function app for a data transformation project. So there are few services (Which we need to make as separate function apps to apply scalability) consumes or shares common cosmos DB, event grid, service bus etc.

So for the design I was following Jason Taylors Clean Architecture
enter image description here

So the structure is like this

Solution
|
---src (Directory)
     |
     --- Domain Layer (Project)
     --- Application Layer (Project)
     --- Infrastructure Layer (Project)
     --- functions
       |
       --- Function1 (project)
       --- Function2 (project)
       --- Function3 (project)
     --- Web Ui (Project)

So each of the functions project and UI is depending on the application layer.

But my concern is whenever a change in Domain layer happens we are required to deploy all the functions as well, isnt it?

Or is there is any best way to handle this scenario? Like no need to deploy the ui or functions when main layer changes?? I have heard some artefacts way.. But not clear that.

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

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

发布评论

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

评论(1

梦屿孤独相伴 2025-01-31 01:58:06

请检查我的发现是否有助于

我经历了 jayson泰勒清洁结构解决方案模板和其他几个GitHub文章。

  • 我相信您的方法在应用程序中实现干净体系结构方面是正确的,因为有很多方法可以启动您的应用程序,并且该应用程序是否能够使用任何类型的演示层启动,例如API,Console或Azure功能。

我已经提到了此 github artern1 and github第2条,我知道您可以在演示层中使用Azure功能来启动应用程序。

  • 上面的文章解释了如何将清洁架构.NET解决方案与Azure功能集成在一起,以利用其运行时,该运行时充当了应用程序的入口。

Please check if my findings help to:

I have gone through the Jayson Taylor Clean Architecture Solution Template and few other GitHub articles.

  • I believe that your approach is correct in implementation of Clean Architecture in your application because it becomes very easy to have many ways to start your application and if that application is capable of starting up with any type of presentation layer like API, Console or an Azure Function.

I have referred this GitHub article1 and GitHub article 2, where I understand that you can use Azure Functions in presentation layer for starting up the application.

  • The above articles explained a bit about how to integrate Clean Architecture .NET Solution with Azure Functions to utilize its runtime which acts as entrance to the application.
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文