The Workflow Engine Architectural Style

E, the work flow engine style. You separate your application logic into typically stateless and rather primitive services that provide a certain functionality. And on the other hand, you describe some kind of work flow, for example, a state machine or an activity diagram. As part of the work flow, the primitive services or actions are called am. The idea is to represent business processes as a first class citizen, and not as something that's somewhere implemented in your application coat somehow. A negative a. Although you could argue whether this is really negative.