Skip to main content

Heterogeneous Cloud Integration


Heterogeneous integration is common scenario in the Enterprises where their IT portfolio is based on heterogeneous platforms. Various solution approaches such as message broker, messaging middleware, SOA – service based integration were employed to address heterogeneous integration challenges.

 

These solution approaches were good when the integration happens on premise, with in the data centers of an Enterprise. Problem here is non-availability of “elasticity”.

 

With the Enterprises started leveraging cloud platforms extensively for various solution aspects such as elastic computing, storage, it opens new capabilities that can be leveraged for heterogeneous integration. Also, similar to existing on premise scenario, Enterprises are also leveraging multiple cloud platforms to address their business needs. This scenario will pose same integration challenges as those that were faced within on premise datacenters

 

Within datacenters / on premise, integration products were expected to comply with WS-* standards to avoid interoperable issues in heterogeneous integrations.

 

AMQP [Advanced Message Queuing Protocol] is a new standard protocol approved by OASIS for messaging solutions. This helps in building heterogeneous integration solutions in the context of (Heterogeneous) cloud. It can be leveraged for complete heterogeneous cloud based integration solutions & hybrid (Cloud + Datacenter – On Premise)

 

Windows Azure provides a capability “Service Bus” for enabling message exchange based integrations. With the support for AMQP 1.0 and availability of APIs in different platforms (Java / .Net), applications on different on premise / cloud platforms can leverage message exchanges based integration through Windows Azure Service Bus using AMQP 1.0.

 

This can help Enterprises to realize their BYOD plans based on devices from various platforms. Enterprise Apps can always leverage queuing & publish/subscribe brokered messaging features of Azure Service Bus as a middleware broker while the devices act as subscribers.
Labels:

Comments

Post a Comment

Popular posts from this blog

Blockchain for a "Secured" AADHAAR

AADHAAR is gradually becoming the “Most Important” digital identity (like a social security number in US) for the citizens of India. It is considered to be more important than any other identities such as Passport, Driving License, PAN card etc. as it is being recognized as the “Mandatory” proof for the authenticity of an Indian citizen, for all the Govt. as well as private transactions, starting from availing the subsidized residential gas benefits  to operating a trading account or even getting a Passport. Because of this, the secured accessibility & immutability of that digital identity is very critical. The AADHAR card once issued to a citizen should not be subjected to change especially in terms of AADHAAR number, name of the person etc.; Any compromise on AADHAR can lead to problems related to mistaken identity. Storing AADHAAR information in a Blockchain platform is a natural choice , as Blockchain offers "Cryptographically" secured decentralized storage and facilit…
4 comments
Read more

SharePoint 2013 Architectural Trade-Offs

When planning for deploying SharePoint 2013 based Enterprise workloads, it should be done with the consideration / awareness of impact of various architectural decisions what we make. As SharePoint 2013 is a flexible platform providing lots of options in terms of configuration of the existing OOB features and development of custom development solutions to address specific business functional needs, care should be taken when making a particular decision and its impact on overall solution. Even though SharePoint is a matured product, the effectiveness of various business capabilities such as Enterprise Social, Enterprise Search, BI, Document Management, Web Content Management, and Enterprise Content Management that will be delivered based on it, in terms of addressing the business requirements depends on architecture planning. Effectiveness here means performance, security, up-time and other architectural qualities like Scalability, Reliability etc. more ...
1 comment
Read more