solving classic problems using SOA
16.10.2006-13:18
a good post about how to solve puzzle architectural/integration/merge problems using soa technologies
[..]
How can you keep a large, redundant, entrenched, heterogeneous portfolio alive and responsive to the business, while building for the future?_The go-forward application portfolio should be services-based, and product offerings should be assemblies (compositions) of services, business processes, events, and user interfaces, packaged by industry, and configurable by end customers.
_For incremental gains (refresh, new features, migration), services and data stores developed for the go-forward application should be injected into the existing applications.
_To facilitate interactions across domains and/or redundant systems, the existing applications should have access to a common integration mechanism.
_Since no one can afford to start from scratch, the existing applications can be mined for assets that serve as providers in the go-forward portfolio.
[ via elemental links ]
2 comments
@snawsi : bahi ya lella
soa : service oriented architecture, sorte d'architecture applicative dediee pour des grands systemes d'entreprise ou au lieu de reecrire partout les metiers et l'intelligence de l'entreprise, on les partage et on les rend reutilisables sans dependance technologique ni structurelle...
l'idee est tout simplement de pourvoir rendre ces systemes capabls a s'interconnecter plus aisement et interagir sans surplus des couts (temps, argent, ressources ... etc).
Si Tom, brabbi, consider the " illetrate IT" people illi ki 7alti, c quoi SOA ? Fahamna brabbi , tekseb fina thweb :p