Service-Oriented Architecture

SOA Manifesto unveiled

Posted in:

Business ROI
Enterprise Architecture
Links
Management
SOA Events
Standards Watch

As mentioned earlier, I had the opportunity to join a group of highly motivated and very smart people at the SOA Symposium in Rotterdam to formulate what is being called the SOA Manifesto. Here is the final version of the document, spelling out the core values and related principles that should be part of service orientation and SOA. Hopefully, they will help guide your thinking on the SOA journey:

SOA Manifesto Service orientation is a paradigm that frames what you do. Service-oriented architecture (SOA) is a type of architecture that results from applying service orientation. We have been applying service orientation to help organizations consistently deliver sustainable business value, with increased agility and cost effectiveness, in line with changing business needs. Through our work we have come to prioritize:

Business value over technical strategy

Strategic goals over project-specific benefits

Intrinsic interoperability over custom integration

Shared services over specific-purpose implementations

Flexibility over optimization

Evolutionary refinement over pursuit of initial perfection

That is, while we value the items on the right, we value the items on the left more. SOA Manifesto Guiding Principles We follow these principles:

Respect the social and power structure of the organization.

Recognize that SOA ultimately demands change on many levels.

The scope of SOA adoption can vary. Keep efforts manageable and within meaningful boundaries.

Products and standards alone will neither give you SOA nor apply the service orientation paradigm for you.

SOA can be realized through a variety of technologies and standards.

Establish a uniform set of enterprise standards and policies based on industry, de facto, and community standards.

Pursue uniformity on the outside while allowing diversity on the inside.

Identify services through collaboration with business and technology stakeholders.

Maximize service usage by considering the current and future scope of utilization.

Verify that services satisfy business requirements and goals.

Evolve services and their organization in response to real use.

Separate the different aspects of a system that change at different rates.

Reduce implicit dependencies and publish all external dependencies to increase robustness and reduce the impact of change.

At every level of abstraction, organize each service around a cohesive and manageable unit of functionality.

posted by Joe McKendrick
October 23, 2009 @ 4:32 pm

Previous Post: Anne Thomas Manes: SOA can be resurrected, here’s how
Next Post: Survey: cloud interest grows triple-fold; cost may not be main factor

Last 10 posts:

Hello, I'm a Cloud... and I'm Enterprise Software (11-25)
SOA Manifesto: Manes explains manifesto's aims (11-23)
Cyber Monday approaches -- should companies clamp down on employee online shopping? (11-23)
Popping the buzzword bubble (11-21)
Panel: do cloud computing economic advantages break down in enterprises? (11-20)
No SOAP for this Navy (11-18)
SOA promotes a sea change for the US Coast Guard (11-17)
SOA helps Coast Guard navigate new tides of homeland security (11-16)
IT project risk aversion 101 (11-14)
Data services may help address a major SOA unknown -- data quality (11-13)