Some people might think that to fit heritage systems (nicer term than legacy) into service oriented architecture, you only need to create services on top of them. My opinion however is that, to acquire real flexibility, the decomposition of the heritage systems is at stake aswell.
As Harry Pierson writes here:
"SOA is a way of implementing IT systems as a web of interconnected yet independent loosely coupled subsystems (typically called services) instead of as big honking systems we have traditionally built that tend to be unwieldy, in-agile, difficult to change and probably obsolete by the time they were deployed."
and I totally agree with that. Simply putting services on top of heritage systems is good for integration and reuse, but not for flexibility.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment