Note that there are some explanatory texts on larger screens.

plurals
  1. USNeil
    primarykey
    data
    text
    plurals
    1. CO+1 for schema details - Whilst a certain amount may be inferred from the statement you provide, knowing whether the schema is fixed (we cannot change its design as part of an answer) and if so what the current schema is, would certainly help.
      singulars
    2. COReading the question again, I think not enough detail is given to know if the OPs product would benefit from being interoperable with, but, that if interop was valuable then focusing on ESB compatibility is likely an unhelpful perspective. Rather any choice of interop strategy should take into account the intended interop scenarios (freq/latency/msg size/etc). This might lead to different approaches from db based integration, to REST, to events over MQ, to sync SOAP, etc... Any ESB ought to be able to work with any of these. The value prop being left to the client to consider in their context.
      singulars
    3. COI'm sorry if it appears snarky. It wasn't intended in that way. In my experience working both in organisations which have adopted these products, and with the products, I have found these & other things to be true for me. The OP, whose question I focused on, seemed interested in whether such a request should be dismissed as a request for buzzword compliancy. My view, which I perhaps should have been more specific & explicit in relaying, is that it can, but that as a marketing angle for a vendor it does have value, if not in a moral sense perhaps.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload