> relational database. This also applies when multiple applications > access the same data (I know, an API would be cleaner, but the ROI for > implementing, say, a SOA interface and adding it to all the > applications is typically pretty bad).
Then again, apart from the transactional aspect, it's pretty easy to expose via RESTfull principles and map resources. And then for versionability, employ the immutable strategy of always bumping the version no. one up. The problem will always be ad-hoc query capabilities although one could imagine an interesting hybrid of LINQ and REST - obviously not trivial with Java as client language though. /Casper --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
