Why Read This
If developers treat service-oriented architecture (SOA) only as Web services standards for better application integration, it can easily result in siloed, point-to-point Web services that solve only short-term, project-level problems. Longer-term application delivery benefits from SOA — such as reduced time-to-market and lower development costs — require cross-project, portfolio-level strategy and planning. SOA is proven in the market — the majority of SOA users say they get enough benefit to expand their use of SOA — but getting it right requires application architects and developers to think correctly about what SOA is and how it adds value. Capturing longer-term strategic value from SOA requires designing around business capabilities, creating a business-aligned foundation for a wide range of other business technology (BT) innovations beyond SOA.
Tags: Application Architecture, Application Development, Business Architecture, Digital Business Architecture, Enterprise Architecture Domains, Enterprise Architecture Strategy & Process, Enterprise Service Bus (ESB), Industry Specifications & Standards, Repositories & Registries, SOA & Web Services, SOA Management & Web Services Management, SOA Platforms