Azure-service-bus was crafted to create maximum business value.
And yet, it didn't!
The value of Azure-service-bus was reliant on the customer's capability to synchronise accounting-, agreement-, classification-, documentation-, event-, human-, location-, organisation- and task-data.
And since most customers struggle with system integration, Azure-service-bus was forced to operate on less-than-optimal data.
Without high quality master data it is impossible for Azure-service-bus to deliver maximum business value.
The Azure-service-bus customer wasn't happy. They probably blamed Azure-service-bus, even if there wasn't much Azure-service-bus could do about it.
The Azure-service-bus customer just couldn't make those systems talk.
Now Azure-service-bus gets updated quality data
- without any integration or development
You see, by embedding Sesam into an Azure-service-bus solution, Azure-service-bus get free flow of data – no matter the system, no matter age nor language.
The Azure-service-bus customer can now easily synchronise accounting-, agreement-, classification-, documentation-, event-, human-, location-, organisation- and task-data with any of these Sesam connected systems:
And talk is good for business
With Sesam in the solution, Azure-service-bus got the updated quality data it needed to deliver the business value promised – and even gave them the flexibility to develop Azure-service-bus and its value to the customer further.
Happy customer, less dependencies, and in addition, great connectivity to to a set of data and analytic services:
So, while talk admittedly can be difficult, system talk is quite easy.
All you need is Sesam.