Database Reference
In-Depth Information
Cloud vendors
There are many cloud vendors, for example, Salesforce.com, Microsoft Azure,
Google
App Engine
(
GAE
), and
Amazon Elastic Compute Cloud
(
EC2
). Salesforce uses a Java-
like language called Apex. The GAE uses Java, Python, PHP, and Go. Microsoft Azure
uses .NET but also supports SDKs for Java, Python, PHP, and NodeJS. Amazon uses Java,
Python, PHP, Ruby, and .NET. NServiceBus supports both the Microsoft Azure Cloud and
the Amazon Cloud. The cloud solutions have many templates that are considered to have
an
out-of-box
(
OOB
) functionality to build the cloud solution. There are also extra mod-
ules that can be installed; many are free, and some require a subscription, such as Sales-
force's AppExchange,
https://appexchange.salesforce.com
.
The supporting engines and
programming languages are used to extend none of the OOB functionalities. These are ad-
ditional modules or applications, for example, which connect additional Salesforce features
into Android or use Google mail.
While many cloud vendors, such as Amazon and Azure, can use NServiceBus to interface
directly into their queuing solution, other vendors, such as Salesforce, which has its own
language Apex, built on top of Java, cannot have NSB access its queues as an ESB engine.
As Salesforce has connectors into other products such as Android APIs and Google mail,
connectors would have to be used to queue through external ESBs such as NSB as well.
Most connectors are built through the use of web services. Some of this methodology is de-
Developing an application from scratch seems easier when developing in the cloud as
many cloud vendors have templates and wizards to create data from scratch. The complex-
ity increases if an on-premise solution has to be migrated to an off-premise cloud solution
that is language dependent. For instance, if you have a .NET solution, moving to Microsoft
Azure may be relatively easy, but moving to Google Apps may require a migration to Java
first. Moving to Salesforce may require multiple migrations to the data first, and then build-
ing the GUI through VisualForce, the Salesforce visual interface, as most of the underlying
infrastructure of the Salesforce cloud, Force.com, is not exposed. For this reason, there are
several tools to move data into Salesforce objects, such as the data loader tool,
ht-
The following screenshot shows a sample VisualForce screen:
