Worker Architecture
Workers sit at the adapter edge: they talk to files, model servers, and channel APIs. Domain scoring stays in the Java Runtime.
Components
- Technology stack — Python 3.14 Workbench backend, Java 25 Runtime (Amazon Corretto 25), optional Ollama / chat containers.
- Integration — HTTP to Runtime (
/invocations,/response,/mcp) and Server APIs. Bind hosts with config, not hardcoded product URLs. - Customization — pre/post-score Java plugins and Workbench deployments, not forks of worker containers.
- Journeys — EcoGentic conversational journeys and campaign channels. See Journey management.
Last updated on