Supporting the smooth shift from legacy components to SOA-enabled (Service Oriented Architecture) ones in enterprise architecture is a key requirement for wide-SOA adoption. An SOA structures large applications into reusable building blocks called “services” that respond rapidly to changing business conditions. For an enterprise, in order benefiting from SOA, they first need to transform their enterprise architecture so that it is at least partially SOA-enabled. However, it is often the case with enterprise that they also hate to dispose their current IT systems so drastically. In such situation, reusing legacy components rather than re-implementing them from scratch for provided SOA-enabled components is a preferred approach to SOA adoption for an enterprise in the real world.
I would like to leave my memos related to my "kung-fu" for some technology insights. Kung-fu doesn't only mean a battle style, but means hacking one's own life.
Wednesday, November 02, 2005
Requirements for shifts to SOA
Subscribe to: Post Comments (Atom)
Array's pointers are reset when the original array is logically copied and thus has 2+ reference counts internally. This doesn't h...
The Rational Unified Process unifies the entire software development team and optimizes the productivity of every team member by putting the...
Great demonstrations of powerful combination of recent deep neural networks applications - stacked hourglass networks for human pose estima...
Post a Comment