Owing to those damn megalomaniac tendencies of mines, across investigating bors & friends, I was constantly looking into ways to tackle this whole topic from a different, better (a.k.a more megalomaniac) angle, that also happens to be fundamentally in line with other (ad)ventures I’m currently working on.
I stumbled over zeebe.io (no personal stake in it, just a nastily great tool for SIG Workflow automation). For which I recently started working on a <wip> golang DDD code generator </wip> that is/will be able to bootstrap an event driven golang backend based on clean architecture and domain driven design with a very crude OPA policy interface.
After having given away myself by those links as a very terrible programmer (I’m not actually one!), there shall be merits to this thinking. In my chasing mind, those concepts amalgamate:
- A DDD framework to very easily implement custom business logic and state as needed (github agnostic! —
@7c6f434c) - A zeebe.io orchestrator through version controlled BPMN2.0 graphical “docplementation” of ecosystem workflows (of any sort and as needed).
- An OPA policy agent enforcing version-controlled and -condocumented policies as suggested in Geistesblitz: Empower our Trust Model through a Policy Decision Agent
… amalgamate into a clean ecosystem workflow automation platform that is superior to other solutions by means of leveraging two-birds-one-shot principles wherever possible, such as BPMN2.0 workflow graphics being dual use (doc and implementation) or having policy decided and implemented upon the same PR (OPA’s rego policy language).
Let me know what you think. Isn’t that too megalomaniac, insane & whatever, but actually a nice idea?