On Fri, 2017-02-24 at 18:07 +0000, Kendall Shaw wrote:
For example, a program that regulates flow of water in a garden sprinkler is probably not a good match for xquery and an xml database.
Funnily enough, sensors these days often report results using EXI, and an embedded XQuery engine might be a fine way to go. People used to use mxquery for such applications. A lot of tooling choice comes down to warm fuzzies and familiarity.
If you're actually querying XML, then an XML database and XQuery do make an obvious choice. I find it can help to say it's a "fast forest store" with XML as an interchange and loading format, to try & prevent the misunderstanding that the software reads the entire database as pointy-bracket XML with each query and is glacially slow. I wish we'd used a forest metaphor for naming XQuery...
Liam