Joe McKendrick has a great post on how system architecture these days is in a state of flux - there are a collection of web services floating around, sort of talking to each other, sort of not - the dream of a streamlined, service oriented architecture seems to be still largely that. He suggests that the secret lies in the repository - in having a central design-time asset where organisations can build out from a single repository to a SOA. Now, I find this interesting for several reasons, but mainly because since I started with TOWER Software, four years ago, I've built several different business systems, and I've never buit a relational db store for any of them - I've alwys just used TRIM Context as the repository. Sure it's designed to manage enterprise content - but that can include custom designed content types that map to a business object, just as easily as it includes a document, or some web content. With the web service interface, and the new ICE framework ...