Database Reference
In-Depth Information
migration is accomplished. For this purpose, NSB is a great solution for marshaling data
and business logic from an on-premise solution for an off-premise solution.
Let's not say that this is a replacement for data warehousing where a central repository is
used for data, but when we update one system with a response of a completed message,
error, or another message that is performing an action through SOA, we update the other
system with the same message as well. The following diagram shows a simple example
where the on-premise contains most of the logic to update a payment through a third-party
service, but the response is sent to the cloud as well that is duplicating some of the ser-
vices to update not only the data but the business processes as well:
This example shows the distribution of the ESB messages to the cloud through the mes-
sage queues. The Azure and Amazon Clouds would easily support this design. However,
some cloud vendors will not expose their queuing mechanisms, and for this reason, WCF
integration could be used as a connector to update the services inside more proprietary
clouds such as Salesforce.
The service method of transferring data is a semi-real-time method of transferring small
amounts of data from one system to another through a secure pipe of HTTPS using digital
certificates. We also know that we can transfer messages through a secure HTTPS gate-
way using NServiceBus. A lot of these messages have very small limits by default; for
MSMQ, we have 4 MB, and the default for WCF is roughly 64 KB. Some of these limits
Search WWH ::




Custom Search