Joe McKendrick writes about "SOA and Cloud bonding: Is this good, or too risky?". Aside from the high-level discussion, the practical question is "how exactly do you connect your SOA to the Cloud?". As Joe McKendrick rightly says, an SOA can be seen as a "private cloud". So how do you connect services from an SOA ("private cloud") up to services exposed by Google, Amazon, Force.com, or MS Azure?
One answer is to use an XML Gateway as a local "integration hub"which connects local applications up to Cloud computing based services. This can be done without coding, using the same drag-and-drop integration which is provided as standard.
That is how you practically make the connection. But what about service usage monitoring, outbound transformation, and security? The answer is that rules for caching, outage-reporting, usage monitoring, and transformation can be applied as policies (not baked into code). Perhaps more importantly, security requirements are addressed. For example, outbound data can be classified according to confidentiality (e.g. "no data which includes medical records can go up to the cloud", or "any identifying data must be selectively encrypted using XML Encryption before the data goes up to the cloud".
The XML Gateway is the glue that provides the bond between the SOA and the cloud.
Thinking lazily about music and discogs
1 day ago