Recently a friend asked me: is Windows Azure a Microsoft Official ASP.net application virtual host?
His specific understanding is this: Windows Azure provides hosting for ASP.net applications, and "cloud computing" is so close to us that as long as the ASP.net application is deployed on window Azure, the previous asp.net applications become "cloud apps"!
What's the deal? This understanding is completely affected by today's social chaos. NET virtual host market forced out. Windows Azure serves as a service for Azure services platform, and if you just use him to store your outdated asp.net apps, it's overkill, waste.
So how should Windows azure be used? It is more than the average virtual host cattle where? That's also from Windows Azure's service architecture.
Roles (role):
It's very important to talk about the role problem first. Without understanding Windows Azure's concept of role, there is no way to understand Microsoft's painstaking "cloud".
The programs deployed to Windows Azure play the following two roles: Web role and worker part.
Web role: As the name suggests, is to provide roles for Web services. Simply put, the Web role is ASP.net applicantion, the cloud version of your local asp.net creator! Supports the HTTPS protocol and provides WCF services.
Worker role: An application that runs in the background. It can access any network resources, data sources, and operate in the background. It never shows up in front of the public (without opening the external access interface), it is ordered to execute without complaint (the queue service's Message Queuing can guide its work), it is like an unknown selfless devotee. You can use the Windows System service analogy with it, once started, has been running in the background. Is that cool? This function is worthy of attention, we see clearly, this is the general virtual host can not provide OH ~ Even Google is proud of the cloud platform Google App Engine, so far has been updated many many times, and never considered let a part of the program in the background long-term operation!
This workder role has a "cloud" concept: The cloud has been quietly running, people on the ground can not see it, but can not do without it.
So, "cloud computing" does not mean that as long as you put "computing" on the "cloud" can be, and thoroughly let "calculation" in the "cloud" run. It includes the following layers of meaning: on the cloud-no local server is required; The cloud is large-the computation can be very large; wherever it is, a rise is a cloud-the application of the Yunping platform can be used no matter where and by what device; hiding in the clouds-its computational process, no matter how complex, is not needed to be seen by users on the ground.
Attachment to Role
Web role and worker role These two children also joined the family of Windows Azure with their families, temporarily including:
Use local storage as a cache
Standard event streams log, warn
Health Report
Oh, these are ordinary virtual host can not have it? "Cloud Host" function is very powerful, matching is very perfect!
Service definition
Programs that live in the new environment of Windows Azure are often puzzled by the question of life: Am I a Web role or a worker role?
This requires us to help them.
Windows Azure uses a type of suffix. csdef file to define a service. Including: Does this service seem to be web role or worker role? Use HTTP or HTTPS? Where to find local storage this in-laws to help? Such information.
The picture is not clear? Please click here to view the original image (larger).
Service revisit
Web role and Worder role these two children, after receiving a reply to their career plans, have raised questions about their career: what should be done?
This requires a service configuration. As the name suggests, is the specific service configuration. We use the. cscfg as the suffix file to save them. It serves as a task similar to the Web.config file in ASP.net, and the task is heavier.
The picture is not clear? Please click here to view the original image (larger).
Well, having said so much, I believe the reader has a clear understanding of window Azure's service architecture. Do not make Windows Azure a normal. NET virtual host. Oh ~ Microsoft will be very hurt after knowing!