Episode 33: Service Oriented Architecture, Pt.2b

Process Integration

Business process integration in Service-Oriented Architecture (SOA) is crucial for maintaining long-term operations. Markus Völter explains that business processes differ from embedded systems as they require persistence and run over extended periods. They often utilize services defined within SOA, creating a natural layering where the process layer sits atop the service layer 1.

Business processes are something that run over a long time. So the state of a business process and all its data must be persistent.

--- Markus Völter

The execution of these processes can be dynamic, allowing for changes without redeploying the entire system. This flexibility is achieved through interpreting process definitions at runtime, which Völter suggests is more adaptable than static service definitions 1.

   

Component Design

Designing process components involves extending metamodels to include specialized components that derive their behavior from business process descriptions. Markus Völter highlights that these components, unlike ordinary ones, are not manually implemented but are generated from state charts, activity diagrams, or other modeling notations 2.

It's just a more specialized component that we are talking about. It takes its behavior from some kind of business process definition.

--- Eberhard Wolff

This approach allows for the creation of various components, such as business rule or validation components, each defined by specific notations. The implementation is then generated, ensuring consistency and efficiency in the development process 2.