Business SOA governance is about the long term transformation of IT to align with the business. This means establishing a clear business architecture and then creating a business SOA governance group who will ensure that vision is followed. This is a powerful group and needs to act in the same way as a judiciary. Their role is not to undertake the work but to enforce the boundaries and rules.
SOA is 10 years old. InfoQ has gathered Jeff Andres, Eric Ballou, Dave Hollander and William El Kaim, all Enterprise Architects with a long experience in SOA, to share their perspectives on where we are and where we are heading, as part of a virtual panel. They talk about Reuse, Business/IT alignment, Governance,...
Four years after the publication of the first SCA specification draft, SCA remains a technology that is not well known or understood. Yet IBM and Oracle have built key product suites with it.Jim Marino and Michael Rowley, both co-authors of the SCA specifications, have published a practical guide to get started with SCA which covers the entire programming model from persistence to presentation.
Kjell-Sverre and Jean-Jacques revisit the concept of compatible contract based on XML, XML Schema and WSDL extensibility to foster service reuse and complement Governance. 29
Alex Maclinovsky explains why his vision of Governance differs from those prevailing in the industry. Based on a precise understanding SOA platforms, he defines a unified view of SOA Governance. 1
In this article, Ian Robinson discusses how consumer-driven contracts (stories for services and unit tests exchanged between service development streams) can strengthen the SOA development lifecycle. 2
After 8+ years of intense research, the promises of BPM have not materialized. We explore here a new architecture blueprint for BPMSs based on assemblies and orchestrations. 22
Michele Leroux Bustamante explains the most relevant WS-* standards used today, their implementation among WS platforms (with a focus on Java and .NET), level of adoption and readiness. 7
Pete Lacey, author of the "S stands for Simple" dialogue talks to InfoQ about the problems he sees with Web services in general, and SOAP, WSDL and UDDI in particular. 31
In a short article, Mark Baker claims the default approach to SOA development fails to properly separate concerns, and describes how this is different in Web architecture. 36
InfoQ's Stefan Tilkov talks to REST evangelist Mark Baker about REST principles, its benefits, and the relationship to Web services. 4
.NET and Java interop can be made really simple using a REST document centric approach. This article demonstrates REST for interop as well as POST-REST. 4