Skip to main content

Why this change

iii is built on three primitives: Workers, Functions, and Triggers. Every concept in the system maps to one of these:
  • Workers are long-running processes that connect to the engine and provide capabilities — HTTP serving, queue processing, cron scheduling, state management, stream handling, and anything else the engine needs to operate.
  • Functions are units of work. A worker registers functions, and any other worker (or the engine itself) can invoke them by ID.
  • Triggers are the rules that cause functions to fire — an HTTP request, a cron schedule, a queue message, a state change.
Before this release, the engine-internal components that provide capabilities (HTTP, queues, cron, etc.) were called “modules”. Meanwhile, the remote SDK processes that register functions were called “workers”. This created a confusing split: two different names for things that serve the same role — connecting to the engine and doing work. Modules are workers. They run alongside the engine, register functions, react to triggers, and provide capabilities to the rest of the system. The only difference was the name. By renaming modules to workers, every component in the system uses the same vocabulary. The engine config lists workers:. The SDK connects workers. The docs describe workers. There is one concept, one name, and one mental model. The previous Worker struct (representing a connected SDK runtime over WebSocket) has been renamed to WorkerConnection to avoid collision.

What changed

Config YAML

The top-level modules: key is now workers:, and each entry uses name: with a short identifier instead of class: with a Rust-style path.
The modules: key is still accepted for backward compatibility, but workers: is the canonical form going forward.

Worker name mapping

Adapter name mapping

Adapter entries inside config.adapter also switched from class: to name: with short identifiers:

Full config example


Rust API

Crate module path

The modules Rust module has been renamed to workers, and the trait definition file moved from module.rs to traits.rs.

Trait renames

Type alias and struct renames

Macro renames

EngineBuilder API

Implementation struct renames

WorkerConnection (was Worker)

The Worker struct that represented a connected remote SDK runtime has been renamed to WorkerConnection and moved to a separate module.

Migration examples

Custom worker

Custom adapter


Migration checklist

  • Rename modules: to workers: in all config YAML files
  • Replace class: with name: using the new short identifiers (see tables above)
  • Replace adapter class: with name: using short identifiers (kv, redis, builtin, etc.)
  • Update Rust imports from iii::modules:: to iii::workers::
  • Update iii::modules::module::Module to iii::workers::traits::Worker
  • Replace register_module! with register_worker!
  • Replace add_module() / register_module() on EngineBuilder with add_worker() / register_worker()
  • Rename any *Module / *CoreModule struct references to the new *Worker / *Manager names
  • Update crate::workers::Worker references to crate::worker_connections::WorkerConnection