The
SOA Manifesto was finally agreed on and "inked" on this
ceremony. Although not a set of earth-changing statements, they would have been a decade ago, it represents a set of common sense from all the more vocal guys in this area.
Personally I couldn't find anything that would leave uncomfortable any of the major players, so the whole lists is too "soft" and "vague" that no one will complain. As I said, everyone had enough time to adapt during the last years. If this is still relevant nowadays? I don't believe so, maybe for their personal curriculum/branding/marketing, but for the industry this will be just a reference to update in the marketing documentation - Everyone already writes those statements in their Marketing lingo.
Where I believe change/impact will happen, will be in the frameworks & languages people will use to collaboratively develop those integration challenges:
- Will we have wiki-style development of contracts? text-based and/or visually? oslo?
- Will we have expressive and simple languages for mapping? Grails/GORM?
- Will we have convention-over-configuration as we didn't had with Indigo/WCF? ADO.NET Data Services?
- Will we have auto-magical-injected-best-practices-guidance like in RoR or MVC?
- And surely everyone will be soa-manifesto complaint, interoperable and extensible!
Now we have a manifesto, proper and extensible plumbing (WS-*), auto translations/representations (SOAP/REST/json), dropped UML&Java to DSLs. It's time for the frameworks & tools to show up now!