Since it’s HTTP-based and very close to the web stack, it’s probably the best fit for App Service. NET 4.5 (2012), the ASP.NET Web API stack, located in the namespace, adopted the REST architectural style over HTTP/S. You’ll also have to make sure your bindings use HTTPS, but once that’s done you’ll be able to use the techniques described later. In other cases, it may be more difficult, for example when using Duplex protocols.
In some cases, it may be simple to move to HTTP since WCF does a good job of abstracting the underlying communication protocols. Unfortunately, App Service is a HTTP-only service, so non-HTTP bindings like NetTcp cannot be used. NET 3.0 (2006), Windows Communication Foundation, found in the System.ServiceModel namespace, is a broader stack that can be used with several different communication protocols. It’s a good fit for App Service, and should be easy to move with the techniques I’ll describe later on. NET 1.0 (2002), the web services stack, located in the namespace, is a basic SOAP implementation over HTTP/S. Newer apps could also be using the ASP.NET Web API stack. Most legacy apps will use either the older web services stack (ASMX) or Windows Communication Foundation (WCF). Let’s now talk about moving legacy backend services that use Windows authentication over to an Azure App Service. In my previous blog post, I covered how to move legacy two-tier applications using Windows Authentication to Azure App Service.
Application Development Manager Mike Lapierre explores moving backend services using Windows authentication to Azure App Service.
0 kommentar(er)
