We are pleased to announce a brand new release of Automatiko - 0.2.0
Amazon DynamoDB can be now used as the data store for state persistent store. It includes both workflow instance state and jobs (timers). It does setup all required tables automatically to make sure the use of it is as smooth as possible. You can read up more on this in Automatiko documentation
Similar to Amazon DynamoDB, Apache Cassandra data store is also available. This opens up for use cases that requires high scalability and multi data center approach. It includes both workflow instance state and jobs (timers). It does setup all required tables and indexes automatically to make sure the use of it is as smooth as possible. You can read up more on this in Automatiko documentation
Event publisher that is responsible for pushing out events that hold workflow instance or user task information can now be easily integrated with ElasticSearch. This enables very powerful option to search by various criteria. In addition to just the events that are being constantly updated (to always represent the latest state), this event publisher allows to push out audit log events that are in append only manner. You can read up more on this in Automatiko documentation
WebSocket event publisher is more for user facing use cases where you would ike to have real time information about worklfow instances and/or user tasks. This event publisher is user context aware so whenever a secrity restrictions are defined in the workflow they are applied. Meaning only authorized users will see data. You can read up more on this in Automatiko documentation
Automatiko takes advantage of latest features of Quarkus and this time it brings support for Dev UI to help developers better understnad what their service is composed of.
When using functions and function flows Automatiko will provide build time instructions about available functions. The instructions will provide
When working with function flows where data is always exchanged in cloud events format, users now have more control over what is used for the type attribute. This in turn controls the routing of events to individual functions. By default it is based either on workflow definition id or for activities based on the activity name. In both cases these are prefixed with package name of the workflow.
Photographs by Unsplash.