We get this question a lot, and have tried to summon some of the key similarities and differences. The models are not incompatible. The main difference is the core focus and values. OW SOA is inward-focusing on how to build great services which are reusable and extensible. [Guerrilla SOA] is more edge-focused, hitting the container, middleware and protocol areas harder.
|[Guerrilla SOA]||OW SOA||Equality|
|The big fight is the evil ESB vendor lock in||The big fight is to teach developers and architects how to build distributed systems and to care about data and real business value|
|Protocol centric approach is a good thing||Protocols come and go, lets be protocol agnostic|
|There will always be spaghetti, let´s be spaghetti friendly||Some things does not change (too much). Let us make sure that we avoid spaghetti in our Business Objects across our SOA and systems. We can limit the spaghetti to the process services of the edge of our SOA.|
|Business driven||Business driven|
|Start small||Start small|
|Middleware is not key (or necessary) for a SOA||Middleware is not key (or necessary) for a SOA|
- WebServices can lead to function oriented services, while REST can lead to a resource oriented architecture. Are both SOA?
- I don't think I understand what's meant with law 4 and 5 (I understand the words, but not what you want people to do and when)
- I think I agree with law 3, Establish service ownership and Key Performance Indicators for your services, but an example of a KPI would be helpful
- I think I agree with law 8, Security is not optional in SOA, but I don't understand what you mean by it yet
- In SOA - Is my customer the same entity as your customer? Is my product list the same as your product list? In which situations?
- [Question still to be asked..]
NB! Feel free to add any question you might have here