DISCUSSION: In-process component to component calls
Brooks explains a new feature that allows two components running on the same host to communicate directly, rather than sending invocations over wRPC/NATS.
This significantly reduces latency from hundreds of microseconds to single-digit nanoseconds.
The goal is to support this direct communication for components on the same host, while still allowing distributed communication via wRPC or other interfaces.
DISCUSSION: Reduce host responsibility and API surface
Brooks discusses the evolution of the wasmCloud runtime crate, detailing efforts to extract parts of the runtime into a new, more modular crate called runtime within the wash repository.
This aims to simplify the host's responsibility, making it primarily focused on component lifecycle management (starting, linking, stopping).
It also introduces a "plugin" system for built-in capabilities (like HTTP server or logging) to be optionally added, rather than being hardwired into the runtime.
