坚持使用单片数据库 [英] Persistance using monolithic database

问题描述

大家好，

道歉，如果我的问题听起来有些天真，但我们暂时没有找到解决问题的好方法。

Apologies if my question sounds a bit naive but we have not found a good solution for our problem for a while now.

我们目前正在考虑将使用SQL 2008数据库的单片内部网ASP.net Web应用程序升级到
内托管的 ASP.net MVC Core 应用程序内部部署服务架构。

We are currently thinking of upgrading a monolithic intranet ASP.net web application using SQL 2008 database to ASP.net MVC Core application hosted inside On-premise Service fabric.

我们已经能够找出前端和微服务业务层的SF实施但是很难找到好的持久性解决方案数据存储。作为一个LOB应用程序，我们考虑将数据保存在SQL 2016
数据库中，并使用Entity-framework Core作为ORM。我们知道在微服务环境中，首选每个服务一个数据库，但是为微服务中的每个呼叫创建一个EF上下文可能会变得非常昂贵并且可能会降低整个系统的速度。

We have been able to figure out the SF implementation for front end and micro-services business layer but are struggling to find a good solution for persistence & data storage. As its a LOB application we are thinking of persisting data in a SQL 2016 database and using Entity-framework Core as ORM. We know in micro-services environment one db per service is preferred, but creating a EF context for each call in micro-service can become quiet expensive and might slow the overall system.

所以可以有人建议我们可以使用任何替代方案或我们可以遵循的任何已证明的模式吗？

So can anyone suggest any alternative we can use or any proven pattern which we can follow for doing this ?

以下是我们的想法的过度简化图：

The following is the over-simplified diagram of what we are thinking :

推荐答案

嗨罗汉。我想确保为您获得尽可能多的信息，因此，我将此查询转发给我们的Service Fabric产品组成员。以下是他们的回复。如果您有任何后续问题，请与我们联系。我很乐意进一步讨论
。 

Hi Rohan. I wanted to make sure I got as much information as possible for you and hence, I forwarded this inquiry to our Service Fabric Product group members. Below is their response. Let me know if you have any followup questions and I am happy to discuss further. 

提供的上下文暗示您在您的现代化之旅中，您可以使用经典的ASP.net Web应用程序，该应用程序托管在您自己的硬件上。

The context provided implies you are early in your modernization journey, for your classic ASP.net web application, that is hosted on your own hardware.

Azure Cloud本机应用程序可让您更专注地提供更快的客户价值在将基础架构管理委派给Microsoft时，您的业务。

Azure Cloud native applications enable delivering customer value faster, by allowing you to focus on your business, when delegating infrastructure management to Microsoft.

作为Azure旅程的一部分，用户通常会接触到Service Fabric; ["一个分布式系统平台，可以轻松打包，部署和管理可扩展且可靠的微服务和容器"]（

https://docs.microsoft.com/azure/service-fabric/ ）。

As part of your Azure journey commonly user’s are exposed to Service Fabric; ["a distributed systems platform that makes it easy to package, deploy, and manage scalable and reliable microservices and containers"]( https://docs.microsoft.com/azure/service-fabric/).

此曝光通常会提示用户参与搜索耗材内容，用于开发和管理Service Fabric应用程序，以及通常发现的内容，例如：

This exposure typically prompts users to engage in searching for consumable content, for developing and managing Service Fabric applications, and commonly discovering content such as:

[服务结构应用程序方案]（ https://docs.microsoft.com/azure/service-fabric/service-fabric-application-scenarios ）

[Service Fabric Application Scenarios](https://docs.microsoft.com/azure/service-fabric/service-fabric-application-scenarios)

[Service Fabric的编程模型概念]（ HTTPS ：//docs.microsoft.com/azure/service-fabric/service-fabric-choose-framework ）

[Service Fabric’s programming model concepts](https://docs.microsoft.com/azure/service-fabric/service-fabric-choose-framework)

[服务架构Web参考应用程序]（ https://github.com/Azure-Samples/service-fabric-dotnet-web-reference-app ）

[Service Fabric Web Reference Application](https://github.com/Azure-Samples/service-fabric-dotnet-web-reference-app)

[Service Fabric和Kubernetes比较]（ https://blogs.msdn.microsoft.com/azuredev/2018/08/15/service-fabric-and-kubernetes-comparison-part-1-distributed-systems -architecture / ）

[Service Fabric and Kubernetes comparison](https://blogs.msdn.microsoft.com/azuredev/2018/08/15/service-fabric-and-kubernetes-comparison-part-1-distributed-systems-architecture/)

[包含现有的.Net应用程序]（ HTTPS ：//docs.microsoft.com/azure/service-fabric/service-fabric-host-app-in-a-container ）

[Containerize an existing .Net Application](https://docs.microsoft.com/azure/service-fabric/service-fabric-host-app-in-a-container)

[Service Fabric Github源代码存储库]（ https://github.com/Microsoft/service-fabric ）

[Service Fabric Github Source Code Repository](https://github.com/Microsoft/service-fabric)

[云服务和服务结构之间的差异]（ https://docs.microsoft.com/azure/service-fabric / service-fabric-cloud-services-migration-differences ）

[Differences between Cloud Services and Service Fabric](https://docs.microsoft.com/azure/service-fabric/service-fabric-cloud-services-migration-differences)

[服务结构最佳实践]（
https://docs.microsoft.com/azure/service-fabric/service-fabric-best-practices-overview ）

[Service Fabric Best Practices]( https://docs.microsoft.com/azure/service-fabric/service-fabric-best-practices-overview)

和[Service Fabric Github故障排除指南存储库]（ https://github.com/Azure / Service-Fabric-Troubleshooting-Guides ）

and [Service Fabric Github Troubleshooting Guides Respository](https://github.com/Azure/Service-Fabric-Troubleshooting-Guides)

这些大量的可支持性内容可以自助开源平台学习和[Azure Service Fabric支持选项]（ https://docs.microsoft.com/azure/service-fabric/service-fabric-support ）
可用于提供业务所需的解决方案开发速度;包括提供解决方案架构参考和软件开发服务。

This vast amount of supportability content enables self-serving your open-source platform learning, and [Azure Service Fabric support options](https://docs.microsoft.com/azure/service-fabric/service-fabric-support) are available to deliver the solution development velocity your business requires; to include offering solution architecture references and software development services.

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