Deployment Options Community
Job Service can currently run in two different configurations, each with distinct trade-offs within the Apache KIE (Incubating) 10.0.0: Independent Deployment – Runs as a standalone container, centralizing scheduling across multiple environments.- ✅ Centralized scheduling
- ⚠️ Scalability challenges (leader-based, single active node)
- ⚠️ Lacks transactional consistency; requires CDC (Change Data Capture) for data integrity.
- ✅ Ensures transactional consistency
- ✅ Integrates scheduling within the runtime
- ⚠️ Still requires a single active leader node, limiting scalability
Considerations
- High Availability: The leader-based architecture ensures high availability but limits horizontal scaling.
- Load Distribution: In compact architecture deployment, general Tasks can be redirected to be executed in non-active Job Service nodes to offload processing.
- Data Consistency: Running Job Service independently requires CDC mechanisms (e.g., Debezium) to maintain consistency.
The Aletyx Difference - the Temporal Intelligence Coordinator
One of the core features of the Aletyx Enterprise Build of Kogito and Drools 10.1.0-aletyx release is that the limitations of the Compact Architecture in the Apache KIE community have been removed with the release of Adaptive Process Architecture is the Temporal Intelligence Coordinator. This Aletyx exclusive feature allows for scalable Intelligent Process Orchestrations containers to be deployed allowing for true Cloud Native Workflow!One of the benefits of using Aletyx Enterprise Build of Kogito and Drools is that truly Cloud Native Process is achievable through our exclusive implementation to scale your containers and workflows in your container platform!