Golem overview

Solution architecture and details.

Golem architecture

Golem is a network of nodes that implement the Golem network protocol. We provide the default implementation of a such a node in the form of the Golem daemon, called yagna.

The nodes in the network can act as providers or requestors. Both the requestor and the provider share the same implementation of the Golem daemon.

The diagram above shows the architecture of the network. For the sake of simplicity, it shows just one requestor and one provider.

Requestor

The requestor logic is implemented as a requestor agent, which is a piece of code that runs on requestor's machine and communicates via REST with golem daemon's http server.

A requestor agent can be written in any language as long as it's able to talk to daemon's REST API. To make things easy for the developers though, we provide two high-level API libraries: yapapi for Python 3.6+ and yajsapi, which is an early alpha of our JS/TS API runnable under nodejs.

Please note the "ALT" frame in the left part of the diagram above: typically the requestor contains application code in only one language. There are two "ALT" frames to show two possible scenarios.

More information on a requestor can be found here:

Provider

The provider logic is implemented as a provider agent which is a piece of code that runs on the provider's machine and communicates via REST with the Golem daemon.

The provider can make its resources available to the requestors with the help of many types of execution units (exe-unit for short). Currently, Golem supports:

  • VM exe unit that runs Docker images and allows for an interaction with the running container,

  • and WASM exe unit that runs WASM code

Please note the "ALT" frame in the diagram above: the provider uses only one exe unit at the same time. There are two "ALT" frames to show two possible scenarios.

More information on a provider is available here:

Payments

The payments between requestors and providers are made through the Ethereum network - using standard ERC20 token transfers or - in the future - using zkSync - a Layer 2 solution that will greatly improve cost-effectiveness.