xslt - Why perform transformations in middleware? -

a remote system sends message via middleware (mq) application.

in middleware transformation (using xslt) applied message. reformatted , there no enrichment nor validation. system consumer of transformed message , xslt maintained team.

the original author of of has long gone , wondering why thought idea transformation in middleware rather in app. can't see value in moving middleware, makes less visible , less simple maintain.

also have thought xslt maintained message producer not consumer.

are there guidelines sort of architecture? has done right thing here?

it bad idea modify message body in middleware. negatively affects maintainability , performance.

the reason of doing trying connect 2 incompatible endpoints without modifying them. require transformation of source content understood destination endpoint.

the motivation delegate middleware perform transformation political 1 (endpoints maintained different teams, management reluctant touch endpoint code, etc.).