JEF Executor microservices host the plugins
- JEF Action and Resource configuration parameters
- JEF Action execution functions and logic
When the services start, they automatically send a notification to register the available versions of actions and resources that they provide. Enterprise consumes those notifications to register the action configurations dynamically.
JEF Actions could reference JEF Resources in order to share Resource configuration parameters.
Flex JEF Executors options
The following executor services are included with JEF. These services, along with the actions they include, are provided as part of Dalet Flex deployments and are maintained by the Dalet Flex team exclusively.
- Flex Job Asynchronous Executor: This service defines and executes a number of Flex JEF plugins.
- Flex Publish Indexer: This service defines and executes Flex JEF plugins relating to Publish / Republish / Unpublish.
JEF Example Executor: This is provided as part of the documentation and ‘Getting Started’ demo project.
Developers can use this project as a reference to create their own plugin executor service. Unlike the other services above, it is not deployed, and is not intended for any real use - just as a reference for development purposes.
When Flex has been deployed, additional Job Executor services could be additionally deployed, for example:
- Flex Solution Executor: A service which executes plugins developed by Flex Solution.
- 3rd Party Executor: A service which executes plugins developed by 3rd Party Dalet Partners.
- Customer Executor: A service which executes plugins developed by customer developers.
Job Executors can scale horizontally through the provisioning of more service instances. JEF will automatically handle and balance job execution across available instances.
Job Executors can scale vertically through new plugins developed and deployed in a single service instance. Plugin developers can define which Actions and Resources are hosted on each Executor instance.