Email	Print Reprint
	add to:
	Del.icio.us Digg Google Furl	Slashdot Y! MyWeb Blink
	TABLE OF CONTENTS Introduction Bob Walker, Gemstone Systems Derek Henninger, Progress Software Robert Greene, Versant Erik Meijer, Microsoft Christof Wittig, db4objects Patrick Linskey, BEA Craig Russell, Sun Microsystems Ten Years from Now? Data -- It's Scary Acronym Soup Business and Social Issues Back to the Social Question Different Viewpoints A Bigger Picture Question? A Service-Oriented Impedance Mismatch? Wrap Up

William Cook, Moderator: This is a bigger picture question that the people were asking:

"What is the impact of Service-Oriented Architectures? How is that going to effect the object persistence?"

But perhaps the question here is: "It moves the data further away from the application. Has it a tendency to do that?"

And one person was asking along those lines "What about data federation and federated queries? Are we going to have an object relational mapper that works over service oriented architecture and over a federated data?"

Patrick Linskey, BEA: I think that those two questions are very, very related. A really interesting thing that Erik mentioned earlier is that, in the service oriented world, I think that the myth of SOA is that developers only coded what this app, everything is beautiful and you use lots of brackets. I think that you still write your services and a number of services are still written in Java or C#. And those services are the things that talk to the database, so then you combine a different bunch of services and the trick is really: a) how do you avoid to too fine grained services? They are so fine grained that the application performance just plummets, everything is just XML and b) when that does happen or whenever we can optimize around it how do you recognize that two different services are talking to the same data store and make optimizations of how to query cross them, how do you do this problem of federating a query.

Taking a single query that spans most of the different data storage solutions, maybe objects, maybe relational databases, maybe LDAP, maybe XML, maybe just services directly, maybe old legacy kick spane frames and puts that together into kind of the something approaching the optimal query path to get all the data for the parts of the puzzle. Sadly, I'm not the best person for b) to talk about that but I know that there is something that is a big focus of one of our team down in San Jose and it's really, really interesting stuff. I think that the kind of service aggregation is really fascinating and piercing the XML barrier is something I'm really interested in. How do you make these services less opaque to the environment they're running in.

Previous Page | 1 Introduction | 2 Bob Walker, Gemstone Systems | 3 Derek Henninger, Progress Software | 4 Robert Greene, Versant | 5 Erik Meijer, Microsoft | 6 Christof Wittig, db4objects | 7 Patrick Linskey, BEA | 8 Craig Russell, Sun Microsystems | 9 Ten Years from Now? | 10 Data -- It's Scary | 11 Acronym Soup | 12 Business and Social Issues | 13 Back to the Social Question | 14 Different Viewpoints | 15 A Bigger Picture Question? | 16 A Service-Oriented Impedance Mismatch? | 17 Wrap Up Next Page

RELATED ARTICLES Securing the Java Core Petascale Tools and Genomic Evolution Legal Compliance: Open Source and Quality Assurance SEI, Army Team Up on Software Testing Nozzle: Counteracting Memory Exploits		TOP 5 ARTICLES No Top Articles.