IBM Developer Blog

Follow the latest happenings with IBM Developer and stay in the know.

Learn how to manage growing IBM Sterling Order Management data on IBM Cloud.

Note: Growing order data – Is it really an issue? This blog is Part 4 in a series.

This blog provides an alternative approach to implement order visibility and search using a change data capture software pattern or technique instead of using IBM Sterling Order Management event extension points described in a previous blog in this series.

Change data capture is a popular software pattern used by databases to track changes in data and perform certain actions. It is employed as a real-time data replication technique that does not require making any code changes in the software application.

The source database must enable transaction logging that is read by a change data capture tool, and the data is pushed to a target data source, which can be another datastore or a flat file. This data is then transformed into an order object required to support the read and search mechanisms. The contents of transaction logs are proprietary to the database management system, so a change date capture tool is used to interpret them. There are many standard tools available in the market, including those from IBM, Oracle, Informatica, etc.

The following diagram shows an IBM Cloud approach to change data capture based on real-time data integration to support the order search mechanism.

Change data capture approach

Note: Similar components from other cloud providers like Amazon, Microsoft, and Google can also be used as desired.

Up next: Part 5 looks at change data capture vs. events.