BPM, EA and Compliance

A few years ago, I was invited to join a debate forum belonging to a group of companies that despite not being involved with the financial segment, discussed the workings of each other’s internal controls areas, SOX compliance and benchmarking practices.

First of all, why were BPM and EA specialists invited to this forum, and second, why am I publishing matters of internal controls in a BPM area that contributes to the subjects of Enterprise Architecture?

Continue reading “BPM, EA and Compliance”

BPM and its contribution to Enterprise Architecture

When employing the homonym “BPM,” it is important to clarify the difference between Technical BPM and Business BPM. Technical BPM covers not only the IT tools for business process automation, but also contributes as another available resource for a company to perfect its process management.

Continue reading “BPM and its contribution to Enterprise Architecture”

BPM in a Microservice World: Part 3

This article was originally published on Diabolical Labs.

Many BPM practitioners are used to utilizing a software suite that has some sort of Process Manager component that has control of the transaction as it progresses through activities. The process is generally authored and visualized graphically in BPMN or BPEL. When applying BPM in the microservice world we don’t have that visibility or control.

Continue reading “BPM in a Microservice World: Part 3”

BPM in a Microservice World: Part 2

This article was originally published on Diabolical Labs.

Back in the early days of “workflow” we had control of the transaction, usually a document, from the start of the process to the end. As IT evolved into the SOA/ESB era, we had a little bit less control but for the most part the process engine orchestrated everything.

There were frequent hand-offs to message queues but normally the message would come back to the process engine so it would continue to orchestrate the process.

The microservice world is different. Instead of having a process engine or an ESB controlling a small number of large services, we have many small services that can potentially send and receive messages or respond to events from any of the other services.

It’s more like a web. One initiating message or event to a particular service could affect the exchange of many hundreds of messages between the microservices before the initial request is considered complete. That can make BPM practitioners a bit uneasy due to the loss of control.

We may not have control any longer but we still can have visibility into the process. We can still apply our usual patterns for SLA and exception management, and human and compensating workflows. This can be accomplished through what I call a “tracking” process.

Continue reading “BPM in a Microservice World: Part 2”