--- In [email protected], Jan Algermissen <[EMAIL PROTECTED]> wrote: > > > > Obviously when designing a system which is meant to stay the course we > > need to make it as adaptable, reusable and evolvable as possible. > > Right. IIRC there is such a system that has proven to be quite well > designed and is has now been around for a decade. > > > That after all is the whole point of SOA. > > Fine, but since there is such a system....why design a new one that > is not even an evolution of the existing, proven one? > > Why use build upon a paradigm (specific interfaces) that is known for > its poor success regarding reusability and evolvability.
I was not suggesting that one should take pain to keep the legacy interfaces; in the example I quoted there are probably no interfaces to keep apart from 3270 screen feeds. It is however sometimes worth conserving the application logic and functionality, or at least a significant part of it. If the truth be known, this legacy logic and functionality is not always fully understood by the current IT staff. To give an example outside the sphere of enterprise apps, I knew a South African company with some brilliant comms technology written in assembler. This stuff had no equal anywhere else at the time. Some of this code, the programmers (not even the highly technical managing director - brilliant but mad) did not dare touch. Why? Because no one understood the algorithms except the brilliant, mad Englishman who had written the code. There was enough technical sanity in the firm not to meddle where dangerous! I suspect that as new technologies, not yet envisaged, come online, you may well eventually have to change your interfaces everywhere. Having built sound SOA structures, many of your application modules will live on, albeit in new skins. Gervas > Jan > > ________________________________________________________________________ > _______________ > Jan Algermissen, Consultant & Programmer > http://jalgermissen.com > Tugboat Consulting, 'Applying Web technology to enterprise IT' > http://www.tugboat.de > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
