--- In [email protected], "reamon943" <rea...@...> wrote: > > I was reading a review of a new book that just came out covering the > architectural aspects of buildings in and around where I live. One of the > comments from the author was about how the architecture of one of the newer > movie theater complexes was considered "throwaway architecture" (or > disposable architecture) but still was a significant aspect of the community. > > This got me to thinking about throwaway architecture and how/if it might > apply to business, enterprise, application, etc. architectures that are > influenced or guided by SO principles.
Well SOA is (to me at least) all about building agile architectures that can be quickly adapted to meet new requirements. Throwaway or disposable architecture implies the building is simply trashed and replaced, as it is too costly to adapt. That may be true with physical buildings - where only the rubble is reused, not the 'components' - but doesn't have to be true with software, which with careful application of SOA and CBD principles is inherently more flexible and the elements of which can be 'reused' in a new instance of architecture, rather than replaced every time. Lawrence
