Day: July 13, 2018

Software products and projects have become more complex today owing to comprehensive product functionality, advanced architectures, and sophistication. Added to this is the increasing business and margin pressure, for which projects are now required to be accomplished within a short time span and with minimal resources. To achieve this, organizations constantly invest in state-of-the-art tools to make sure that every single stakeholder has the proper ammunition for on-time delivery with quality. Though organizations invest heavily in individual tools, and many projects continue to fail, leading the organizations to incur a huge loss.

Why is this? Poor visibility of proper metrics is one of the major factors behind this. With data residing in silos, generating proper metrics involving data from across various tools is a huge challenge resulting in poor control and inaccurate decision making. https://goo.gl/tTHRR2 #DataIntegration #ML

#ICYDK: In my previous article, I explained one of the messages flows in detail from the point of view of implementing in- and outbound messaging with Spring Integration’s AMQP support. I briefly mentioned that data handler adapters are loaded dynamically, and they’re plugged into the message flow. In this third part, we’ll explore one of those technical challenges in detail that the application’s modular design raise and how it can be tackled by using Spring Boot 2’s new property Binder API.

What Will You Learn After Reading This Article?

For most of the use cases, having a predefined, static message flow is sufficient. However, that’s not the case for the forget-me app, as multiple data handlers can be configured, which will carry data erasure out. One major challenge to address is deciding whether or not a particular data handler needs to be initialized and plugged into the main message flow. I can tell you beforehand that Spring’s conditional configuration will be used to do that. https://goo.gl/i4rxob #DataIntegration #ML