Where did the summer go? Since our User Forums in Chicago, London and around the world in May and June, we've been sharing with clients our vision and roadmap for the future of IBM Master Data Management and time has flown by. I can't believe its already August. If you aren't in the know, reach out to me and we'd welcome the opportunity to share our vision and roadmap with you as well. But in the midst of this travel, we've also been working on some enhancements that we have recently released in IBM MDM v220.127.116.11 - our latest Feature Pack (FP10).
This latest Feature Pack brings a number of enhancements to the utility used to publish your master records for further analytical use cases and searching on the graph database as well as what we released in April, the Operational Cache. The functional enhancements cover security controls between components and introduce a simplified single system deployment options for trial purposes.
In addition to these functional enhancements, the MDM Publisher stack architecture has been simplified and optimized, delivering the following improvements:
- Support for horizontal scaling of bulk loads through the use of Kubernetes Spark scheduler, Spark pods, and HDFS pods.
- The ability to deploy the publisher in a Kubernetes cluster of its own, outside of the Operational Cache Kubernetes cluster.
- A 10x improvement in start up and showdown times down to an average of 30 seconds.
- Smaller overall image size.
The Operational Cache itself benefits from similar security and simplification enhancements, as well as the replacement of Solr with ElasticSearch Indexing to be more aligned with our RESTful API strategy. For full details on these and other enhancements, check out the InfoSphere MDM V11.6 Knowledge Center collection.