Doorgaan naar hoofdcontent

Cloud to Cloud Application Integration






A lot of applications have integration possibilities, so do cloud applications. The question I got from a customer is whether to have a point-to-point integration with Cloud applications or to go through their ESB solution. This blog describes some considerations.





Context
The customer has a HRM application in which job vacancies are managed. Furthermore that system also handles the full applicant process flow. They also have another cloud application that handles the job vacancies. This application posts the jobs to social sites and other channels to promote the vacancies. Furthermore this application has some intelligence for job seekers to advice some new vacancies based on previous visits or profiles. The job vacancies need to be sent to the Vacancies application and applicant information needs to be sent to the HRM application, when a job seeker actually applies for a job. Furthermore status information about the job application is also sent back. This flow of information is depicted in the next figure.

Integration options
Several options are discussed to integrate these cloud applications.
Point-to-point
The two applications have an out-of-the-box integration possibility, so integrating this way is easy.

However also consider:
  •          Dependent on the cloud suppliers to integrate on infra level
  •          Monitoring is not conform the guidelines of your company. Maybe there is no monitoring at all.
  •          Exception handling is not conform the guidelines of your company, so what happens when something goes wrong on integration level
  •          What happens when one cloud application is migrating to another version? Maybe the other application must migrate as well, and maybe this is not what you want.
  •          Security: what are the security possibilities of the applications and the integrations? Is this conform company standards? Is this conform regulation requirements?

This option is viable if it is seen as one application function, in which you can see it as 2 modules within the same application. Furthermore integration is taken care of by the two cloud suppliers.
Enterprise Service Bus
In case more control is needed for the integration and job vacancies are also interesting for other applications to integrate (job boards), the ESB solution can also be an option. A lot of companies are still using ESB i.s.o. Microservices architecture. They still have a lot of old applications which need adapters to decouple the systems.


Advantages of this solution:
  •          Use of common business entity on the ESB to decouple applications
  •          Monitoring conforming company guidelines
  •          Exception handling conforming company guidelines
  •          Reuse of services possible
  •          Reuse of events for other interested applications
  •          Company can decide which parts of the application APIs are used

Note that the ESB can be cloud and on-premise.
Disadvantages:
  •          Extra layer
  •          Company must setup the infrastructure connections themselves


Conclusion
Depending on your requirements, guidelines and timing constraints, there are always several options for integrating cloud applications. Considerations:
  •            Flexibility information delivery (decoupling)
  •            Own connection infrastructure control
  •            Monitoring requirements
  •            Exception handling requirements
  •            Security and compliance requirements
  •            Upgrading cycles of cloud applications

Feedback is always welcome!


Reacties

  1. Cloud to Cloud Application Integration is explained with examples and pictures making it more understandable.

    BeantwoordenVerwijderen
  2. Thank you for sharing the article. The data that you provided in the blog is informative and effective.
    Best Devops Training Institute

    BeantwoordenVerwijderen
  3. Cloud to Cloud Application Integration is clarified with models and pictures making it more reasonable.

    Cloud Deployment Solutions

    BeantwoordenVerwijderen
  4. I have been searching to find a comfort or effective procedure to complete this process and I think this is the most suitable way to do it effectively.
    data science course in malaysia

    BeantwoordenVerwijderen

Een reactie posten

Populaire posts van deze blog

OSB 10gR3 and SWA and MTOM

This blog is about using soap with attachments and the use of MTOM within the OSB (10gR3). A service is created that accepts a soap with attachment (DocumentService) and translates it to a service that accepts a binary element. MTOM is used for performance reasons for the second. Some notes: * For the use of attachments you need RPC-style document instead of the usual document-style. This due to the fact that the document-style limits a message to a single . * A service can not have both SWA and MTOM within OSB. First a WSDL is setup for the DocumentService: The $attachments variable holds the attachments and the body holds the attachment data. Also other data is stored within the attachment element (see h

Microservices mindmap

"The tree" - See also   my photo page When you are fairly new within the Microservices land, there are a lot of terms fired at you. So also for my own understanding i have made a mindmap. I think it has a good status now, so that i can share it with you. As always feedback is very welcome ! You can download the mindmap here .

Book review: Data Management at Scale (Piethein Strengholt)

 This blog is a review of the book "Data Management at Scale (See also at bol.com ) Data Management is a hot topic nowadays and this book does a fantastic job at adding value to this topic. It is a must read and one of the few technical books I finished reading in a weekend. The book gives a fantastic overview on how to implement a Data Mesh data architecture. The Data Mesh concept is explained by Martin Fowler here . The book is a good mix between conceptual and implementation architecture level. It gives a lot of examples of how this architecture at scale can work, for both small and big companies. It is practical and I used it to implement it at one of my customers. The book describes an architecture in which the focus is on the DIAL (Data- and Integration Access Layer).  On a high level the book covers the following topics: The key principles for data management at scale - Domain-Driven Design  - Domain Data Stores - Meta data management Ready Data Store The concept of servin