你建议什么服务架构？ [英] What service architecture Do you suggest?
问题描述
我正在为基于网络的会计等商业项目寻找稳定的架构，
数据库： SQL Server
平台：.Net和C＃编程语言
技术：Windows Form
所以它包含大约200个表和几十万个记录，这个软件将以两个版本生成：
组织内部版本 （桌面）：
有可能其中一个分支机构距其他分支机构更远，需要使用它并且它具有有效的IP。在大公司的最终版本中，可以同时插入几个Warehousing和一些用户（10到15）的可能性。
基于Web的版本：
这是针对额外的组织报告，这些挑战在桌面版中更多。毫无疑问，我需要自定义模型我的架构，但我选择了Entity Framework作为中介模型。
所以我的问题：我是否使用基于服务的架构用于桌面版？是否需要？或者我不需要它因为所有数据库信息都是
读取并被移动to down和SQL基于基于网络的服务？
如果我需要面向服务（我选择WCF用于面向服务），那么必须放置像authenticate和transactions这样的代码吗？那么选择，删除和更新呢？
嗯，现在的问题是，在面向服务的架构中;首先我们必须为每个类创建一个数据协定类，我们必须把类放在一起。考虑到交易方法，我们至少有2000种方法，它们的管理难度为
。
你有什么建议？ Odata等数据服务怎么样？它是否支持现有需求？从速度和稳定性的角度来看，它是否适合基于组织的
网络？ ？
我对服务和数据服务没有任何问题并且知道所有这些，但我的问题是选择项目的架构。使用MVC模型和控制器类连接到数据库或选择服务。
如果是WCF服务，那么很难处理代码（由于有一个类）。现在我们有数据服务，但是我不确定桌面版的速度和稳定性。有人可以帮助我并与我分享他的经验吗？
打扰一下我的英语不好。
提前致谢。
很多问题，我将首先关注'桌面'版本。数据有多大？如果服务不可用会怎样？
I’m looking for a stable architecture for Commercial Projects like Accounting based on Network,
Database: SQL Server
Platform: .Net and C# Programming language
Technology: Windows Form
So it's Contain at about 200 tables and Several hundred thousand Records, this software will be produced in two versions :
Intra organizational version (Desktop):
It’s possible that one of the Branches has been located more far from other, needs to use that and it has valid IP. In Final version for big companies, there are concurrent insert for several Warehousing and some users (10 to 15) possibility.
Web based version:
It is for extra organizational reports which these challenges are more in desktop version. There is no doubt that I need customize models in my architecture, but I've selected Entity Framework as mediator Model.
So my Question: Do I use Service Based architecture for Desktop version? Does it need? Or I don't need it due to all database information are read and are moved to down and SQL is base on network-based services?
If I need service oriented (I selected WCF for service oriented),The codes like authenticate and transactions must be place up? What about Selects, Deletes and Updates?
Well, now the problem is, in service oriented architecture; first we have to create a Data Contract Class for Each class and we have to cast classes together. And with consider transaction methods, we have at least 2000 methods and their management will be difficult.
What’s your suggest? What about data services like Odata? Does it support existing needs? Does it suitable for Intra organizational based on network from speed and stability point of view?
I have no problem with service and data services and know all of them, but my problem is choice the architecture for project. Connect to database using MVC Model and Controller classes OR select the service.
If WCF service, well handling the code will be difficult (due to have one class). Now we have Data Service, but I’m not sure about speed and stability in desktop version. Can anyone help me and share his experience to me?
Excuse me for my bad English.
Thanks in advance.
Lots of questions, I'll concentrate on the 'desktop' version first. How old can the data be? What happens if the services are unavailable?
这篇关于你建议什么服务架构？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
