title: Architecture Considerations
body: <p>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).</p>
  
  <p>My questions ...:</p>
  
  <ul>
  <li><p>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?</p></li>
  <li><p>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?</p></li>
  </ul>
  
  <p>Your responses will be highly appreciated.</p>
  
  <p>Thanks.</p>