Lists Home |
Date Index |
> The bit I found most interesting was from Daniela Florescu: "I don't think
> have good performance as long as we have people marshalling data from XML
> Java and back," Florescu said.
Daniela's comment about performance was in response to a question about
whether we'll have the right database technologies to support wide-scale
deployment of Web services --
- 2+ billion people with portable phones and wireless devices using Web
- potentially half a billion to a billion concurrent database connections
for some applications
- millions of documents being exchanged daily for e-biz.
My question was whether we could optimize XML querying to support processing
on that scale.
This was after citing two data points using current query technology on
- 1.15 seconds to return 50,000 rows with an SQL SELECT
- query 2-3000 documents per second with XQuery.
> So, I can kinda, sortof see a programming model that handles declarative
> stuff easily, encourages a functional programming style, handles both
> XML and relational data "natively", and allows data to be either
> in objects (or aspects?) or exposed for generic manipulation.
> She went so far as to predict that eventually,
> an extension of XQuery will replace both Java and SQL."
More specifically, she said this was not likely in five years, but probable
within ten years. She also talked about us moving to a more declarative
Several of the panel members agreed we're still in a building block phase
with XQuery. In the future, there will be sophisticated tools that use
XQuery as an enabling technology (just as we've seen with SQL).