Implementing Executor Services

Job Executors (sync, async, resources) own and host the action configuration / action executors (resource configuration / resource executor). When the services start, they automatically send a notification that says whether the action / resource can be executed. Enterprise consumes those notifications to register the action configurations dynamically.

Types of JEF Executors

Three different types of executor are included with JEF. These are as follows:

  • Synchronous Job Executor: This service executes short running actions. This service along with the supported actions is provided as part of Dalet Flex deployments and is maintained by the Dalet Flex team exclusively.
  • Job Asynchronous Executor: This service executes long running actions. This service along with the supported actions is provided as part of Dalet Flex deployments and is maintained by the Dalet Flex team exclusively. Developers could create new Job asynchronous executor services to extend JEF capabilities with new action plugin support.
  • Resource Executors [for future release]: Resources are special types of job asynchronous executors. These have the additional responsibility of managing external systems, along with asynchronous job execution.

Executor Services Included with JEF

The following executor services are provided as part of JEF:

Name Description
Job Sync Executor service A service that is responsible for executing short running actions. This service along with supported actions is provided as part of Flex deployment and maintained by the Dalet Flex team.
Job Async Executor service A service that is responsible for executing long running actions. This service along with supported actions is provided as part of the Dalet Flex deployment and maintained by the Dalet Flex team
JEF Example Executor This is a simple action provided as part of the documentation and ‘Getting Started’ demo project. Developers can use this project as a reference to create new job async executor.