Part I can be found here.
TL;DR - maybe thinking in "processes" is a relic of traditional, policy-driven, hierarchical enterprise? Decentralised model, based on business events & reactions tends to have some advantages & seems to match modern architecture principles better. WHAT IF we ditch BPM completely?
Is there a better way?
There are at least few scenarios that seem to fit modern
.Disclaimer: by "architecture in the wild" I mean situations (I've personally encountered) where sheer reality surpasses known (& somehow theoretical) standards / patterns :) in a way that does not impose any obvious solution. It doesn't mean (usually) that everything is so utterly broken, in majority of cases these are completely valid scenarios. With a twist ;D.
TL;DR - microservices, low coupling, cross-functional teams, continuous
.NET world is lacking a good BPM solution based on Microsoft stack. That’s why if I hear about BPM projects, it’s usually something in Java. We (my current employer) haven’t sold many projects like that in Poland, but we have few minor credentials. As those references are based on jBPM (mainly version 4.x), what we tend to propose to the