> For the complete documentation index, see [llms.txt](https://docs.teller.org/teller-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.teller.org/teller-1/node/overview.md).

# Overview

Description of Teller's Distributed Cloud network

Telller's network of distributed cloud nodes operate as Proof of Cloud (POC) consesus validators for the Teller Protocol. In other words, the nodes act as a data router for the protocol's smart contracts.

The current system architecture looks like the following:

![](https://3004295493-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MCFeD1LoLRehnuodvA7%2F-MHxQTvf-4_HVHBnPZhp%2F-MHxRDUPj60Wlyw8t8Ko%2FArchitecture-v1.0.png?alt=media\&token=f0315624-e161-442a-a63f-740cf7273280)

The three core components of the distributed cloud network are:

1. The Teller Subgraph
2. Teller Contract Event Listener
3. Teller Web2

## Subgraph

Teller's Subgraph listens for events emitted through interactions with the protocol's deployed smart contracts, and then parses them to a graphQL service. The instructions and repo can be found in the link below:

{% embed url="<https://github.com/teller-protocol/subgraph>" %}

## Contract Event Listener (CEL)

Contract event listener (CEL) will read and store all the data that the subgraph generates into a local postgres database to be consumed by the node.

{% embed url="<https://github.com/teller-protocol/contract-event-listener>" %}

## Web2

Web2 is the primary web service endpoint of the node, which handles the user requests via a RPC JSON v2.0 service.

{% embed url="<https://github.com/teller-protocol/web2>" %}

## Kubernetes

All of these components are deployed and distributed via docker images using kubernetes, which is in turn packaged as a helm chart installation:

{% embed url="<https://github.com/teller-protocol/teller-node>" %}

The system architecture diagram is as follows:

![](https://3004295493-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MCFeD1LoLRehnuodvA7%2F-MI1wY3rU8q97F51Om6b%2F-MI4_gLT4jYeFFYbc_cm%2Fimage.png?alt=media\&token=c80b752c-f0e1-4b1c-a141-36de34839572)

{% hint style="info" %}
The Node manages everything inside kubernetes cluster:
{% endhint %}