This is a continuation of Order Search Service – An Implementation Strategy. The earlier entry focused on using the existing integration between IBM Order Management and IBM Universal Behavior Exchange (UBX) as a data exchange platform in IBM Cloud to provide a better user experience while business continues to grow with more transactions.

This blog targets implementations where the choice of cloud platform is different than IBM like, Amazon Web Services (AWS), Microsoft Azure or Google Cloud Platform (GCP). This blog will also present an option to implement the solution on premise.

IBM Order Management uses event extension points to establish an integration with IBM UBX. The event extension points can also be extended to implement a customized logic and producer for open source tools like Apache Kafka, Kinesis in AWS, Event Hub in Azure, PubSub in GCP and so on.

Event based data integration patterns for the transaction data type and Scheduled Cron based process for master and configuration data, as established previously, can also be used with other cloud providers. The following diagrams show reference components that can be used to achieve a similar outcome in AWS, Azure, GCP and so on.

Note: The components displayed in the following diagrams are not benchmarked and can be swapped with alternates as needed based on non-functional requirements.


Figure 1: An Amazon Web Services Approach

 


Figure 2: A Microsoft Azure Approach

 


Figure 3: A Google Cloud Platform Approach

 

An option using common open source tools for implementations that may want to retain all data on-premise is shown below.


Figure 4: An Open Source Approach

 

Up Next: Order Search Service – A Change Data Capture Perspective

2 comments on"Order Search Service – Taking it beyond IBM Cloud"

  1. I have a question about the first design that uses AWS services. Is it possible for UBX endpoint to continuously call a REST API whenever there are events? Push from UBX to an API.

Join The Discussion

Your email address will not be published. Required fields are marked *