XSLT is by and large single-threaded, and most jobs in the print domain get horrifyingly ginormous due to basic conceptual flaws of XML/XSL. Your Operations guys might have a panic attack when they see how that impacts on the server side. But then, to mitigate that, someone's going to need to cook a queueing system with some kind of notification/email doohickey, and now the InfoSec guys are also having a panic attack.
You're probably going to save money, end of the day, just homebrewing some XSL drop ins with a real programming language.
I gotta say, as a mostly-defense XSL guy[1] who also knows his way around TS and Py, this is probably going to be a real boom time to kick this dumb XSLT work to the curb and do some high dollar contracting making JS/TS drop-ins for govcons and defense.
[1] Who also thinks XSLT is a joke told by an idiot. My morale? Oh, it's great.
You're probably going to save money, end of the day, just homebrewing some XSL drop ins with a real programming language.
I gotta say, as a mostly-defense XSL guy[1] who also knows his way around TS and Py, this is probably going to be a real boom time to kick this dumb XSLT work to the curb and do some high dollar contracting making JS/TS drop-ins for govcons and defense.
[1] Who also thinks XSLT is a joke told by an idiot. My morale? Oh, it's great.