So much written on SOA and Web Service, unfortunately, again and again, we get it wrong. so I decided to put them in a simeple set of rules.
Rule 1: Service is an Interface
Service is an Interface, not a method; it is a way to open your application or your core engine to external application.
Think Service as a User Interface, before writing service, think about who is going to use it, how they are going to use it.
Rule 2: What is exposed is more important than how it is exposed
Give importance to define the document/data structure and service signature
Many times, we are end up arguing whether to expose services as a plain method call, RPC, or SOAP, instead of think about what exactly we are going to expose.
Rule 3: SOA is not just Web Service
Web Service is one way of exposing your services; don’t start your SOA implementation with Web Service in mind.
For more information on this line, read Common Misconceptions about Service Oriented by Architectures by Werner Vogels, CTO of Amazon.com
Comments