Database Reference
In-Depth Information
Not only can you deploy websites and virtual machines, but you can deploy other applica-
tions as well, such as services that live in the cloud, which are called cloud services. These
can be servers or other types of services that a person would normally deploy on a server.
For instance, a backend process such as NServiceBus could be considered a cloud service.
IIS running in the cloud is considered a cloud service. Many of the web services running
in the cloud will be considered cloud services.
The cloud service also must have a role to run the service. There are two main roles to run
cloud services: one is the web role to run IIS, and websites built in PHP and CGI, and the
other is the worker role that is more geared to run backend processes or backend cloud
services. Both roles can run the .NET framework services, native code, and the Windows
Server services.
A cloud service can be published or packaged from Visual Studio. To publish a cloud ser-
vice, built in the Azure SDK, it will package and deploy the cloud service to your Azure
cloud services.
Another method to deploy a cloud service is to package it locally and upload the pieces
into the Azure cloud services to deploy it interactively with Azure.
Depending on the cloud vendor, you can determine your development methodology. We
have provided some small examples for developing in Salesforce. While developing in
Google Apps, you can use the Eclipse IDE in Java, Apache Tomcat, and the Mule ESB
on-premise, and then upload it to the Google Cloud. For Azure, you can develop your
solution on-premise as well as in Visual Studio, and then upload it and run it from Azure
Cloud. However, for Azure, you will need cloud development packages. There is a cloud
service package, which is a development ZIP file that will be deployed in a
.cspkg
format. It will need to be deployed with a cloud configuration file as well, which is in the
.cscfg
file format.
