Another 'setting the scene' issue is related to the fact that there are about as many SOA definitions out there as there are SOA experts. These definitions range from as narrow as possible (just XML webservices) to as wide as possible (BPM based orchestration of IT service components dependent on business process usage, e.g. in BPEL).
In this blog, we are explicitly looking at the widest definition of SOA: We are interested in SOA because its orchestration based on business processes using BPM/BPEL etc. can provide great value (especially if combined with MDA). In our definition, the SOA ESB does not have to be implemented using XML webservices, instead any middleware that meets the requirements could be used. ESB is also quite a badly defined term - we will mainly use it for a collection of (several) middleware technologies, registries, repositories etc.
So this definition may explain why we will be talking about business processes etc. quite a bit.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment