Cloud Integration Solution Diagrams

eTECHaaS Oracle Cloud File Based Integration

Last couple years, I have worked on several cloud integrations, which are for different kind of requirements. I am sharing some of the integration architecture diagrams, which I designed for the cloud integration projects. Hopefully, the solution diagrams are useful to some of you, for designing your integrations.

Today, there are several Paas offerings, which assist in integration to Saas applications, apart than other useful functions.

Cloud Integration using Paas DB & UI

Typical Paas Based Integration uses PAAS DB to stage data for enrichment purpose and PAAS REST API Implementation, and PAAS Java or WebApp Services like Oracle Java Cloud Service (JCS) for building UIs.

eTECHaaS Oracle Paas Based Integration
eTECHaaS Oracle Paas Based Integration

Platform as a service – PAAS

Before we move to other integration architecture diagrams, it would help to get an understanding on Paas. In previous diagram, we used Paas as a staging area for processing data (or enriching data) before integration into Saas. We can use custom jobs or apis to validate and enrich data records. And we can develop UI as a custom application to enrich records in a form.

Note: There can be different offerings in Paas for Integration, Process, UI/forms & Database. You can select the paas offerings based on your requirement.

Paas Cloud Integration Flows

PAAS DB is not required when the data can be immediately integrated to Saas application, i.e. when data enrichment does not require any manual intervention or is not deferred. Alternatively, we can use Paas Integration platforms like Mulesoft CloudHub or Oracle Cloud Integration (OIC) to build integration between systems.

We have employed 2 flows for each integration: –

  • Source system Trigger Event flow
  • Process to Saas flow
eTECHaaS Oracle Cloud Trigger Integrations
eTECHaaS Oracle Cloud Trigger Integrations

This logical design shows the various JSON messages involved in the integration flows.

Notable is the Business message JSON, which is the common JSON format. If you have same integration (i.e. Order Creation integration) between multiple systems, you can use a common JSON for all the Order Creation flows irrespective of the system. This also means that you would have to study all the systems to design a common message structure. It is not so complex as it sounds, though.

File Based Integration

It is a common practice to use File based integration for batch updates to cloud. It employs below integration flows in the diagram: –

  • Process Files to Paas / Saas
  • Process Paas to Saas
eTECHaaS Oracle Cloud File Based Integration
eTECHaaS Oracle Cloud File Based Integration

I will be writing on Integration Design, Technical Architect, Solutions, Use Cases, Programming Logic, Design Patterns and also sharing some of my own project management templates. So stay tuned or drop me a message in case you are interested on these topics.


2 Responses

  1. Highly energetic blog, I enjoyed that a lot. Will there be a part 2?

    Feel free to surf to my homepage APJ Solicitors

  2. Joesph says:

    I know this if off topic but I’m looking into starting my own weblog and was curious what all is needed to get set up?

    I’m assuming having a blog like yours would cost a pretty penny?

    I’m not very web savvy so I’m not 100% sure.
    Any recommendations or advice would be greatly appreciated.

Leave a Reply