Section 11.3. Conclusion


11.3. Conclusion

In this chapter, we explained the motivation for an SOA introduction and the main benefits related to such an introduction. Many enterprises adopt an SOA in order to increase agility. SOAs are seen as a means of breaking up inflexible IT infrastructures, which are usually characterized by monolithic applications. The flexibility of an SOA, its modular and decoupled development process, and in particular its potential for application reuse enable enterprises to reduce their project risks and to achieve a faster time-to-market.

Obviously, SOAs are not a magic bullet, solving all problems of enterprise projects with a single strike. Only if the environment is right can an SOA yield the maximum effect. However, SOA does, if applied correctly, minimize the risks of enterprise IT by providing a sound architectural basis.

Introducing an SOA will in general be a long-lasting process, and its beneficial effects will become apparent not all at once but steadily during this process. Only at the end of the process will the Agile Enterprise become a reality.

References

[Sta2001] Standish Group. Extreme Chaos. http://www.standishgroup.com/sample_research/PDFpages/extreme_chaos.pdf, 2001.

URLs

http://www.de.cgey.com/servlet/PB/show/1004690/07.16.02%20Studie%20Web-Services_G.pdf

http://www.standishgroup.com/



    Enterprise SOA. Service-Oriented Architecture Best Practices
    Enterprise SOA: Service-Oriented Architecture Best Practices
    ISBN: 0131465759
    EAN: 2147483647
    Year: 2003
    Pages: 142

    flylib.com © 2008-2017.
    If you may any questions please contact us: flylib@qtcs.net