Engineering
The Flowable Engine as a Serverless Function: Part II
Flowable core developers Filip Hrisafov and Joram Barrez continue the Flowable + serverless journey by looking at other technologies that make a serverless “process as a function” possible.
In part 1, they discussed what serverless is, its challenges with regards to the Flowable engines and demonstrated implementations using Flowable with Spring Cloud (including running it on AWS Lambda), Micronaut and GraalVM.
In this follow-up part, they look closer this time at implementing such a functions using Flowable combined with Spring Fu and building a native image with GraalVM. The end result is an incredible 13 milliseconds bootup time for a full-fledged Flowable-powered function!
Optimizing end-to-end business automation can be a tall task for legacy systems that lack integration abilities such as APIs. But robotic process automation can provide a successful interim transition to replacing these when time to market is crucial.
Enterprises need to process a large volume if documents daily — quickly and accurately. Flowable uses Intelligent Document Processing (IDP) to improve content processing and support enterprises in managing documents end-to-end.
CMMN was mainly designed with case management in mind to handle dynamic, human-driven processes, where the execution is not always a straight line, but might involve human decision to drive the process forward. But it can do way more than that.