架构的考虑 [英] Architecture Considerations

问题描述

我目前正在设计一个Web应用程序，我使用和python-的Django前端的C＃-WCF实体框架在后端考虑。我的核心竞争力是C＃，后端技术，因此选择。但是，我不想使用C＃在前端，因为我preFER Django的简洁的设计VS ASP.NET加上动态语言的灵活性。我打算REST调用为所有数据访问WCF服务（即我不会使用Django模型都可以）。

I'm currently designing a web application and I'm considering using python-django for the front end and C#-WCF-Entity Framework at the back end. My core competence is C#, hence the choice of back end technologies. I, however, do not want to use C# at the front end because I prefer django's clean design vs ASP.NET plus the flexibility offered by a dynamic language. I intend to make REST calls to the WCF service for ALL data access (i.e. I won't be using django models at all).

我的问题...

• 这是一个很好的架构，在可扩展性方面？是否有明显的，项目威胁缺点的架构？它会更好简单地使用ASP.NET和忘记REST调用？

• Is this a good architecture, in terms of scalability? Are there glaring, project-threatening disadvantages to the architecture? Would it be better to simply use ASP.NET and forget about REST calls?

该架构还提出了关于托管，因为它很难找到一个Django主机也做.NET的担忧。将托管在谷歌应用程序引擎的前端，并在Windows Azure上的后端是一个明智的做法？

The architecture also raises concerns about hosting since it's difficult to find a django host that also does .NET. Would hosting the front-end on Google App Engine and the back end on Windows Azure be a wise thing to do?

您的回答将是非常美联社preciated。

Your responses will be highly appreciated.

感谢。

推荐答案

我会建议通过减少您使用的technoligies的数量简化架构。

I would recommend simplifying the architecture by reducing the number of technoligies that you are using.

在特定的使用ASP.net MVC的前端，而不是蟒蛇。

In particular use ASP.net MVC for the front end instead of python.

使用WCF到您的前端和后端之间comunicate。使用肥皂或REST是那么只是一个配置更改。

Use WCF to comunicate between your front end and backend. Using SOAP or REST is then just a configuration change.

当您使用REST来谈谈你的后台，你有​​自己的托管，或使用Windows Azure中的选项。

When you use REST to talk to your backend, you have the option of hosting it yourself or using Windows Azure.

这篇关于架构的考虑的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！