liveBook · Manning

NATS

As explained in Server-Side WebAssembly

NATS is a lightweight, high-performance messaging system and broker for communication among distributed software components.

NATS is a lightweight, high-performance message broker for communication among distributed software components. In wasmCloud, it forms the lattice that lets hosts communicate and coordinate across environments. section 6.1

Within a wasmCloud application, NATS supports:

  • Communication between components running on the same host or on different hosts. section 6.1
  • Runtime linking, with wadm dynamically establishing and managing component connections. section 6.1
  • Coordination across a distributed network of wasmCloud hosts. section 6.1

Hello World lattice

Running `wash up -d` starts NATS in the background at `127.0.0.1:4222`, alongside a wasmCloud host and wadm monitor. A deployed HTTP component then communicates through the lattice with an HTTP server capability. section 6.1

How Server-Side WebAssembly covers it

How deep it goes
Defines NATS and explains its lattice role, but does not descend into broker protocol internals.
Examples
Uses a wasmCloud Hello World deployment, local startup output, component links, and the NATS endpoint at 127.0.0.1:4222.
What it assumes
Assumes familiarity with wasmCloud applications, hosts, components, capabilities, and wadm deployment manifests.
What you can do after
Operate/configure a local wasmCloud lattice, verify NATS startup, inspect logs, and stop the platform.
How it connects
Ties NATS to wasmCloud hosts, lattices, wadm, runtime linking, and distributed components.

Also explained in

Compare how 2 books explain NATS →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Server-Side WebAssembly. The section links point to the parts of the book it draws on.