1. Theses on SOA

2. SOA SOA is much more than architecture SOA is a new paradigm,
a new way of thinking.

3. SOA SOA favors Darwinistic governance
SOA transforms IT landscapes from autocratic rulings into democratic governance, where market-oriented and Darwinistic principles and strategies make the tone.
For those who have forgotten about Darwin: it is
“Survival of the fittest”
That is not necessarily the most powerful

4. SOA favors collaboration
SOA is a collaboration infrastructure that does not only allow for collaboration but encourages the latter by making it easier to reuse common components over the web instead of building isolated silo solutions.
SOA favors collaboration

5. SOA SOA implies agility The infrastructure must provide the tools
Agility to change business processes in real-time is one of the core visions of a Service Oriented Architecture. The infrastructure must provide tools to guarantee stability of the existing world while components are in permanent transformation.

6. SOA SOA is not bottom-up nor top-down
SOA is neither bottom-up nor top-down but a healthy blend of both.
It will be the duty of the management to drive the vision and to orchestrate and mediate the daily changing situation

7. SOA fails by too much governance
Plans are the natural enemy of any SOA. While you can use some standard template to implement the most wanted and needed services you cannot control the growth of a SOA without risking throttling its further evolution. Like democracy cannot be ordered by a dictating ruler, SOA cannot be ordered from the top. SOA lives and dies with the participation and non-participation of the community members.

8. SOA has no purpose on its own
SOA has no purpose on itself but to assist the developers to build and transform business process quickly.

9. SOA SOA requires developer satisfaction
We welcome the Ruby on Rails mission:
“Ruby was created for maximum developer satisfaction.”