Nodes and Workers
Ockam Nodes and Workers decouple applications from the host environment and enable simple interfaces for stateful and asynchronous message-based protocols.
Last updated
Was this helpful?
Ockam Nodes and Workers decouple applications from the host environment and enable simple interfaces for stateful and asynchronous message-based protocols.
Last updated
Was this helpful?
At Ockam's core is a collection of cryptographic and messaging protocols. These protocols make it possible to create private and secure by design applications that provide end-to-end application layer trusted data.
Ockam is designed to make these powerful protocols easy and safe to use in any application environment – from highly scalable cloud services to tiny battery operated microcontroller based devices.
However, many of these protocols require multiple steps and have complicated internal state that must be managed with care. It can be quite challenging to make them simple to use, secure, and platform independent.
Ockam Command makes it super easy to create and manage local or remote nodes. If you run ockam node create, it will create and start a node in the background and give it a random name:
Similarly, you can also create a node with a name of your choice:
You could also start a node in the foreground and optionally tell it display verbose logs:
To stop the foreground node, you can press Ctrl-C. This will stop the node but won't delete its state.
You can see all running nodes with ockam node list
You can stop a running node with ockam node stop.
You can start a stopped node with ockam node start.
You can permanently delete a node by running:
You can also delete all nodes with:
When a worker is started on a node, it is given one or more addresses. The node maintains a mailbox for each address and whenever a message arrives for a specific address it delivers that message to the corresponding worker. In response to a message, a worker can: make local decisions, change internal state, create more workers, or send more messages.
You can see the list of workers in a node by running:
For example, nodes that are created with Ockam Command come with some predefined services including an example service /service/uppercase that responds with an uppercased version of whatever message you send it:
Services have addresses represented by /service/{ADDRESS}. You can see a list of all services on a node by running:
Later in this guide, we'll explore other commands that interact with pre-defined services. For example every node created with ockam command starts a secure channel listener at the address /service/api, which allows other nodes to create mutually authenticated secure channels with it.
When you run ockam enroll for the first time, we create a space for you to host your projects.
When you run ockam enroll for the first time, we create a default project for you, within your default space.
Like other nodes, Projects offer services. For example, the default project has an echo service just like the local nodes we created above. We can send messages and get replies from it. The echo service replies with the same message we send it.
Ockam , , and help hide this complexity and decouple from the host environment - to provide simple interfaces for stateful and asynchronous message-based protocols.
An Ockam Node is any program that can interact with other Ockam Nodes using various Ockam protocols like Ockam and Ockam .
You can create a standalone node using Ockam or embed one directly into your application using various Ockam . Nodes are built to leverage the strengths of their operating environment. Our implementation, for example, makes it easy to adapt to various architectures and processors. It can run efficiently on tiny microcontrollers or scale horizontally in cloud environments.
A typical Ockam Node is implemented as an asynchronous execution environment that can run very lightweight, concurrent, stateful actors called Ockam . Using Ockam , a node can deliver messages from one worker to another local worker. Using Ockam , nodes can also route messages to workers on other remote nodes.
Ockam run very lightweight, concurrent, and stateful actors called Ockam Workers. They are like processes on your operating system, except that they all live inside one node and are very lightweight so a node can have hundreds of thousands of them, depending on the capabilities of the machine hosting the node.
Note the workers in node n1 with address echo and uppercase. We'll send them some messages below as we look at services. A node can also deliver messages to workers on a different node using the and its Transports. Later in this guide, when we , we'll send some messages across nodes.
From ockam command, we don't usually create workers directly but instead start predefined like Transports and Secure Channels that in turn start one or more workers. Using our you can also develop your own workers.
Workers are stateful and can asynchronously send and receive messages. This makes them a potent abstraction that can take over the responsibility of running multistep, stateful, and asynchronous message-based protocols. This enables ockam command and Ockam to expose very simple and safe interfaces for powerful protocols.
One or more Ockam can work as a team to offer a Service. Services can also be attached to a trust context and authorization policies to enforce attribute based access control rules.
Ockam Spaces are infinitely scalable Ockam in the cloud. Ockam Orchestrator can create, manage, and scale spaces for you. Like other nodes, Spaces offer services. For example, you can create projects within a space, invite teammates to it, or attach payment subscriptions.
Ockam Projects are also infinitely scalable Ockam in the cloud. Ockam Orchestrator can create, manage, and scale projects for you. Projects are created within a and can inherit permissions and subscriptions from their parent space. There can be many projects within one space.
Ockam are programs that interact with other nodes using one or more Ockam protocols like Routing and Secure Channels. Nodes run very lightweight, concurrent, and stateful actors called . Nodes and Workers hide complexities of environment and state to enable simple interfaces for stateful, asynchronous, message-based protocols.
One or more can work as a team to offer a . Services can be attached to trust contexts and authorization policies to enforce attribute based access control rules. Ockam Orchestrator can create and manage infinitely scalable nodes in the cloud called and that offer managed services that are designed for scale and reliability.
If you're stuck or have questions at any point, .
Next, let's learn about Ockam's and how it enables protocols that provide end-to-end guarantees to messages traveling across many network connection hops and protocols boundaries.
