Hi @RicknBaker

It is an unusual approach, a more integrated approach would perform a translation of XML to OMM, see the description in the Mapping FIX to OMM White Paper.

If you publish data in XML format then it is effectively opaque data; the infrastructure cache cannot apply updates to it. If update semantics are required you would disable caching in the infrastructure and implement it in the publisher and consumer.

Hi @RicknBaker

OMM Generic messages can carry custom payload including XML, although best approach would be to publish your data in OMM domain messages. There are some predefined RDM like YIELD_CURVE (22), which might be a suitable structure for your application, or else, there is the ability to define your custom models.

Also, Elektron API's are recommended for any new projects.

Thanks for the info guys. As our data will be so disparate (Over 35 different types) and as it won't update very often, I'm thinking I might just use OMM to notify the consumer that new data is available, and then provide a REST interface that the consumer can call to get the actual data. Does this seem sensible?

I would avoid double interaction - when the client is already listening for updates, might as well deliver the payload in the update message as well.

I agree with Gurpreet, the additional interaction/dependency may also have a negative impact on resilience of your application.