Hi Marco,
Just like you, I fell in love with XQuery and BaseX several years ago.
I had the opportunity to put BaseX into production twice. Each time, it was live in production before the team had started wondering how to architecture the whole thing in a J2EE way.
And each time, for political reasons, the XQuery solution was eventually replaced with a J2EE one.
IMHO because CTOs never like to see their tooling decisions challenged, and mainstream software engineers cannot imagine there could be an alternative to the TDD/J2EE/imperative language solution, when they are not simply thrilled by the elegance and power of XQuery/REST-XQ.
Maybe a solution could be to directly speak to business oriented people, that will appreciate how fast you can provide them with solutions.
A JSON promising solution might be the N1QL language upon Couchbase.
Best regards, Fabrice Etanchaud
-----Message d'origine----- De : basex-talk-bounces@mailman.uni-konstanz.de [mailto:basex-talk-bounces@mailman.uni-konstanz.de] De la part de Marco Lettere Envoyé : mercredi 22 février 2017 13:43 À : BaseX basex-talk@mailman.uni-konstanz.de Objet : [basex-talk] Somewhat unusual question
Hi to everyone,
probably this is not the right place for such a discussion but the BaseX communitiy is the one I'm better introduced to and the one I trust the most. So I hope that this somewhat unusual excursus will anyway be of interest to some of you.
As for myself I fell in love with XQuery and its power in terms of data manipulation many years ago. I wouldn't change it with anything else and BTW we're using it (thanks to the incredible BaseX runtime) much beyond data-processing being it the backbone of all our micro-service oriented architectures.
Now, to the point, in the near future I probably will be called to face a somewhat skeptical customer who will argue about the technological choice of XQuery.
My point will be to make a comparison with the technologies they're currently using and I would like to demonstrate that for a rather XML- (and in general data-) intensive workflow XQuery is perfectly suitable and probably better than many other alternatives.
I would tend to exclude XSLT because it would face similar opposition. I would also exclude languages at a lower level of abstraction like Java, Python, Javascript, C/C++ and so on for obvious architectural reasons.
But then only templating languages/engines come to my mind. Those would still be probably novel technologies to learn and wouldn't offer the structural, syntactic and semantic power of XQuery anyway.
So I ask you kindly, in order to complete my preparation on these matters, is there anyone that has experience with other tools or languages that can be compared with XQuery when used for XML querying, generation, transformation, templating, composition and so on?
Thanks a lot!
Marco.