The impact on communications as it evolved from individual email messaging to social networks, both in business world as well as in personal life’s is pretty obvious. Take a pause to digest this: every 60 seconds in 2016, 40+ years old workhorse of communication aka email had ~150k messages sent in 2017, against 5 years old newbie known as WhatsApp’s ~29,000k messages.
While it is debatable what % of either of them carried any business value or even any meaningful content, there is no doubt that the communication approach has evolved from point to point messaging to networks based publishing /subscription based on relevant topics communication.
As business technology follows the evolution path of personal technology, the interest is growing on the topic of integrating organizations to networks (eg, Ariba / Coupa etc networks & online marketplaces like Alibaba.com) & how is that different from using B2B / EDI communications. The answer we feel lies in the Metcalfe’s law, which projects that impact is not additive but exponential to the number of connected participants.
As an important integration pattern, we evaluated the same using the Fluid-Integrations evaluation model. Obviously, the traditional sender / receiver based messaging is being mostly being evolved to the network based models though latter is characterized by lower volume / higher frequency of interchanges.
Enabling the pub/sub model using traditional EAI tools like SAP PO / CPI is doing a catch up act & cloud native applications like AWS SNS are showing the path ahead, especially when it comes to integrating on a network model.
Here’s a sample of settings needed to send data from on-premise EAI tool to a JMS based pub/sub system on premise. Key difference form regular communication is the Queue/ topic support.
Main capabilities for pub/sub model are topic support, Push Delivery, support for diverse protocols including REST, replication to multiple receivers, topic filtering, message durability, security / encryption, scalability & HA and ability to support microservices.
A hybrid integration of on premise EAI with AWS cloud based SNS / SQS is supported using custom adapters provisioning connectivity and topic support.
Why should we care? Future of Fluid-Integrations will probably follow very similar path of personal communications ie, network driven, topic based, hybrid infra, short lived messages at high velocity and happening in realtime. Who says millennials are not showing the way for progress?