Service-Oriented Architecture
Whether you call it "dynamic IT", "on-demand" or "adaptive” architecture, the concept of Service-Oriented Architecture (SOA) has been swirling through IT conferences of late. SOAs provide the ability to create a connected environment that moves information from system to system in addition to allowing the broad reuse of services. This loose coupling of resources makes the model more flexible than traditional system architectures. The concept can be difficult to grasp, but the impact is clear: These methodologies are fundamentally changing the way we build our internal systems. According to a July 2005 Goldman Sachs survey of 100 CIOs, 87% currently use Web services and 54% plan to deploy infrastructure to support SOA by 2006.
To stay on top of the trend, get daily insights delivered to you.
Service-oriented architecture issues covered in FierceCIO include:
- Case studies on good approach to SOA
- Cost benefits of SOA
- Managing change needed to move to service-oriented architectures
- Experimenting with web services
- Security concerns with web services
- Addressing loose coupling for a scaleable SOA
- Building new IT assets to be SOA-ready
- Pros and cons of an ESB (enterprise service bus)
The number of varying expert opinions and analyses are vast, making the need to understand the often-confusing world of service-oriented architectures more essential. If you can adopt the methodologies and best practices of SOA technologies, you can stop reinventing the wheel, automate more, and do more with the applications you already have.





