I want to deploy the backend WCF service in Webber with only internal endpoint in Cloud Service 1 in Webberl. And deploy the ASP.NET MVC frontend in Webberol in Cloud Service 2.
Is it possible to use the Ezur virtual network to call backend from the internal endpoint?
Renewed: I'm just trying to build simple SOA architecture like this:
yes and no.
An internal endpoint essentially means that roll insensively is configured to accept traffic on a given port, but that port can not receive traffic outside of the cloud service (hence This is "internal" for the cloud service). Internal end points are also not balanced, so those who call you will need "handcuffed" traffic management.
The problem now is that where problems arise, a virtual network allows you to safely cross the cloud service boundaries, by calling a roll event in the Roll Event in Cloud Service 1 A roll instance is called in the cloud service. However, to do this, calling role examples need to know how to get the examples of how to be addressed. If they were in the same cloud service, they could crawl the cloud service topology through the Rolene environment class. But this class only works for the cloud service, there is no information about its virtual network.
Now you can publish the role example in your FQDN a shared area (called Azure table storage). However, a cloud service only uses its own internal DNS resolution (which allows you to resolve short names only in a single cloud service) unless you configure a virtual network with a self-hosted DNS server Are there.
So yes, you can do whatever you can, but seeing that it offers some challenges, I have to argue that the additional complexity of the solution to the separation facility for the deployment is correct Can be held? If so, then I also see and see if maybe two services are a direct call (like Qatar-based pattern) rather than interconnecting between each other.
Comments
Post a Comment