Concepts
When you ran the hello example in the TypeScript or Python quickstart, you were already using most of Naylence’s core ideas:
- a fabric that routes messages,
- a node that hosts agents and connects to the fabric,
- and at least one agent that receives a message and does something useful.
This section puts names to those pieces so the rest of the docs have a clear vocabulary.
Core Concepts
- Fabric – The messaging layer that connects everything.
- Nodes – The hosts where agents live.
- Agents – The units of logic that send and receive messages.
- Sentinels – Special nodes for routing and security.
- Clients – Code that initiates interactions.
Mapping concepts to the hello examples
Here is how the quickstart examples line up with these concepts:
- Fabric – the object you create at the start of the program; it routes messages to agents.
- Node – the process that created the fabric and registered the agent.
- Agent – the class or function you wrote (
HelloAgent) that logs the incoming message. - No sentinel yet – all of this runs in one process, so there is no separate routing node.
As you read the rest of the docs, you can keep this mental mapping in mind:
- Fabric → the message bus,
- Node → where agents live,
- Agent → a unit of behavior with an address,
- Sentinel → an edge node that routes and protects the fabric.
Next up:
- Topologies – see how these pieces are arranged in different deployments.
- Guides → From single-process to two-node fabric – turn the hello example into a client ↔ sentinel ↔ agent setup.
Last updated on