I am in Muenchen, Arabella Sheraton Hotel, where the first day of the W-JAX conference takes place. This conference is one of the biggest conferences in the german area. The SOA management day, as the name implies, concentrates on Service Oriented Architecture.
The session "BPEL schon einsetzbar?" focused on current problems with the different notations used for business processes. One of the most used notation in the past was the EPK ("Ereignisgesteuerte Prozesskette"). This notation is the simplest approach to model business processes. From the technical point, the EPK is not the best choice, because it contains no technical information. Here, the new BPM notation (swimlanes, loop constructs) provides a better way to model technical aspects. A process model based on the BPMN can be transformed in a BPEL process, because the BPMN has all necessary constructs to develop BPEL. This session also shows that companies often rape BPEL, because they use BPEL for wrong processes. BPEL should be used to model the business process and nothing else.
SOA, currently a hype issue, solves all problems, as it is written in books, magazines, presented on conferences. A critial and interesting session was the one of Dr. Gernot Starke. He discuesses the following problems on SOA projects:
- SOA projects are big projects
- Different stakeholders (IT and Faculty)
- No or less experience
- Many Risks (time pressure, new technologies)
- There are too many standards
- Loosely coupling is not realy realized (Point-To-Point communication between Web Services)
- XML is everywhere (Slow performance)
As my previous blog announced, SOA is not a technology. SOA is a business first approach: The management must know their business processes and how to deal with them. And more imporant is, the governance, which must be planed in an accurate way.