The Infosys Labs research blog tracks trends in technology with a focus on applied research in Information and Communication Technology (ICT)

Main | Connecting Aristotle to Distributed Security.. »

Architecture and Design considerations for BPM using SOA

In today’s enterprise business processes are often created from services. Creation of business process from services has been greatly facilitated by platforms providing run times for business process languages (e.g. BPML, BPEL etc) and architectural paradigms like SOA. These platforms and software components greatly facilitate development, deployment, monitoring, NFR requirements management and life cycle management of services/processes. Usage of services for creation of business processes has distinct benefits in terms of extensibility of process/ service, managing SLA, implementing change back models at finer level of granularity etc to name a few.  In order to address such varied requirements practitioner architects often come up with ingenuous architectures or design to address an overall requirement or a specific issue.
Frankly, a given solution can be trivial or elegant architectural proposition, but valuable all the same and hence the need for sharing such best practices with larger community. I will be discussing on architectures/ components/ tips for BPM implementations using SOA.
I am looking forward to the Designer, Architect and practitioner community to share their unique experiences, in terms of business requirement and proposed architectural and design considerations in BPM solutions.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on