After several years of existence, SOA continues on without a full consensus opinion on what exactly SOA is. A recent presentation at Gartner AADI Summit by Yefim Natis started a never ending debate about relationships/differences between SOA and integration.
Martin Fowler suggests that following the open-source model for developing software, might be a good way to solve the problem of "Who is responsible for the incremental development of cross functional/departmental services?"
One of the prerequisites for successful SOA implementation is an understanding of the business problem that will be solved and building a business case for the implementation.
Gartner analysts have written a letter from a fictional SOA architect/engineer to their CEO/CTO explaining why SOA has failed for them. Even though it is a work of fiction it does cover some interesting points.
During the past several years industry tried to define and redefine SOA many times, often contradicting itself in the process. Is SOA really changing that much, or all this is happening due to continuing lack of understanding of what SOA really is?
Red Hat has released a new version of the JBoss Enterprise SOA Platform (version 4.3) and a new version of JBoss Operations Network (2.1). The new SOA Platform allows for the remote monitoring and management of open source SOA deployments while the new integrated management platform aims to improve cooperative support.
In his new article, Jonathan Mack provides a first-hand insight on meeting SOA challenges from business, technology and organizational points of view. He defines key components of successful SOA, major implementation obstacles, and the ways to overcome them.
Starting a SOA Governance organization is arguably difficult. Too much of it and people will try to avoid it while not enough of it will make people question its value. We review the answers provided by industry experts who share their experience.
Although many companies today are banking on SOA to help them respond faster to new and changing demands of the economic landscape, they are not always capable of achieving consistent measurable results. A recent white paper from IBM defines five best practices to achieve success with a SOA implementation.
Assaf Arkin questions a recent report indicating SOA failures and Joe McKendrick of ZDNet examines the meaning of SOA failure in his article.
Complex Event Processing systems and Event Driven Architectures have been identified as playing a larger role in sophisticated systems today and in the future. What that role is and how it is carried out are up for debate.
Gartner analysts have observed increased adoption of the following 5 SOA design patterns * Multi-channel Applications * Composite Applications * Business Process Orchestration * Service Oriented Enterprise * Federated SOA
A typical SOA implementation is as much about solving business and organizational problems as it is about technology. A latest SOA survey by Burton group shows that unless these three SOA underpinnings are balanced correctly, SOA implementations are destined to fail.
The SOA Working Group contributed to the Open Group a draft version of SOA Ontology 2.0. The standard defines a formal ontology for Service Oriented Architecture. The ontology is written in the Web Ontology Language (OWL) and contains classes and properties corresponding to the important concepts of SOA.
Fred Cummins, an EDS fellow, and SOA veteran, wrote an essay last week on "Data Management for SOA". He is looking at how some of the key tenets of service design ("loose coupling" and "autonomy") relate to enterprise data in the context of achieving reuse and enabling change.