Hardware Machine¶

Purpose¶

The Hardware Machine provides a standardized interface for engines to interact with the underlying hardware components of the physical machine Anoma nodes are running. By decoupling engine software from specific hardware implementations, the Hardware Machine abstracts away complexities and facilitate cross-platform compatibility, enhancing software development and deployment.

Background¶

Historically, developers that wanted to write a program had to know how each underlying hardware device communicated with the rest of the system to ensure the software's compatibility. With a hardware abstraction layer developers can just talk to the operating system what the hardware device should do, which then generates hardware-specific instructions to the device. Anoma's Hardware Machine thus provides an interface for accessing hardware-related resources such as CPU, memory, and storage.

Scope¶

For V1, we assume that the Hardware Machine provides other engines access to local storage, compute, time management, and logging functionalities of the physical machine an Anoma node is running.

Overview¶

The current Hardware Machine is composed of the following five engines.

Local Storage Engine¶

The Local Storage Engines provide efficient data storage and retrieval mechanisms directly on the physical machine of an Anoma node. These engines are specialized to meet distinct requirements of data storage and retrieval from other engines.

Local Logging Engine¶

The Local Logging Engine provides capabilities for recording, monitoring, analyzing, and managing events and activities locally on the physical machine that the Anoma node is running. It supports diagnostic efforts, security monitoring, performance optimization, and historical analysis to ensure the stability, security, and efficiency.

Local Wall Clock Engine¶

The Local Wall Clock Engine provides a mechanism for tracking and managing time locally on the physical machine that the Anoma node is running. It abstracts away the details of the underlying hardware and provides an interface for getting real-time clock functionality.

Communication Diagram¶

sequenceDiagram

%% --8<-- [start:sequence]
Any Local Engine ->>+ Any Hardware Machine Engine: Operation Request
Any Hardware Machine Engine -->>- Any Local Engine: Operation Response
Any Hardware Machine Engine ->>+ Local Logging Engine: Append Log
%% --8<-- [end:sequence]

An engine communicates with the Hardware Machine by sending a request to one of its engines to perform a specific operation. The Hardware Machine engine executes the operation by interacting with the underlying hardware components and returns a response. It also logs relevant events and communicates them to the Local Logging Engine.