THEPROCESSFOUNDRY

A concept for a BPMN microservice framework with a focus on the developer's user experience (UX). As with all frameworks, this one sucks. I would welcome the help to make it suck less. uI'm currently writing smaller (ha … smaller) tools such as Grapht, PivoTable, and NomNomicon... Most of my projects tend to be automation of wrapping APIs and CLIs (I know, essentiaally the same thing) and wiring them together. To reduce all the boilerplate, I'm abstracting each one into set of Actions and Events that can be securely routed to each other. Hopefully, this hideously complex idea will make things simpler in the long run... Grapht: A distributed, yet local, cache. I've found that once I've gotten the info I need from a server, I still need to slice it up and reorganize it based on user clicks, which always needs to be written. Having it in shared memory allows for . It's meant to reduce network load by being able to use ephepmeral storage to re-query previously retrieved data.