...
22
collections/web4/executor/executor_terraform.md
Normal file
@@ -0,0 +1,22 @@
|
||||
## Executor TERRAFORM
|
||||
|
||||
> Terraform is a mechanism on how to deploy IT workloads in a reproducible and safe way.
|
||||
|
||||

|
||||
|
||||
A terraform script has multiple parts and can get deployed by an executor.
|
||||
|
||||

|
||||
|
||||
See the ThreeFold Technology book to learn more about how to use smarts contracts for IT and deploy any workload.
|
||||
|
||||
### Consensus Owned & Deployed Solutions
|
||||
|
||||

|
||||
|
||||
<!-- ### Example with Pokt.Network
|
||||
|
||||
 -->
|
||||
|
||||
|
||||
> Coming H1 2023
|
19
collections/web4/executor/executor_vlang.md
Normal file
@@ -0,0 +1,19 @@
|
||||
# Executor VLANG
|
||||
|
||||

|
||||
|
||||
VLang is an exciting language sponsored by ThreeFold. VLang has 27000 github stars and we believe its a very good language to build executor functions with.
|
||||
|
||||
Why did we choose vlang as a first language to support on the TF Executors?
|
||||
|
||||
- Its a very fast language (minimal energy & cpu footprint)
|
||||
- Its easy to learn
|
||||
- It compiles very fast
|
||||
|
||||

|
||||
|
||||
### Utilization
|
||||
|
||||
- As smart contract language inside chosen blockchain
|
||||
- As provisioning layer for TFGrid
|
||||
- As serverless function layer for Executors (super exciting)
|
12
collections/web4/executor/executors_peer2peer.md
Normal file
@@ -0,0 +1,12 @@
|
||||
|
||||
## From Client Server to Peer2Peer
|
||||
|
||||

|
||||
|
||||
Peer2peer is the most decentralized way to experience our digital life.
|
||||
|
||||
- all executors talk to each other over private secure links
|
||||
- there is no blockchain involved for the compute, storage & network requirements.
|
||||
- each executor needs compute, network and storage resources this is managed by L0 Validators.
|
||||
- The executor (web4 or twin) is the only entity who has control over the resource it requires, its all 100% private and fully peer2peer.
|
||||
|
9
collections/web4/executor/executors_usecases.md
Normal file
@@ -0,0 +1,9 @@
|
||||
## 3 INITIAL USECASES FOR EXECUTORS
|
||||
|
||||
- IPFS
|
||||
- distributed storage location service
|
||||
- we add: reliability, locality, cost effectiveness, …
|
||||
- TERRAFORM EXECUTORS
|
||||
- Smart contract for IT
|
||||
- WEBGATEWAY
|
||||
- Bridge web protocols to internal compute workloads
|
BIN
collections/web4/executor/img/consensus_deployed_.jpg
Normal file
After Width: | Height: | Size: 333 KiB |
BIN
collections/web4/executor/img/executor_arch1_.jpg
Normal file
After Width: | Height: | Size: 426 KiB |
BIN
collections/web4/executor/img/peer2peer_executors_.jpg
Normal file
After Width: | Height: | Size: 427 KiB |
BIN
collections/web4/executor/img/storage_layer_ipfs_.jpg
Normal file
After Width: | Height: | Size: 304 KiB |
BIN
collections/web4/executor/img/terraform_iac2_.jpg
Normal file
After Width: | Height: | Size: 318 KiB |
BIN
collections/web4/executor/img/terraform_iac_.jpg
Normal file
After Width: | Height: | Size: 331 KiB |
BIN
collections/web4/executor/img/terraform_pokt_.jpg
Normal file
After Width: | Height: | Size: 322 KiB |
BIN
collections/web4/executor/img/vlang.png
Normal file
After Width: | Height: | Size: 364 KiB |
BIN
collections/web4/executor/img/vlang_executors_.jpg
Normal file
After Width: | Height: | Size: 438 KiB |
15
collections/web4/executor/storage_ipfs.md
Normal file
@@ -0,0 +1,15 @@
|
||||
## IPFS storage integration on Web4
|
||||
|
||||
> IPFS is a standard used in the blockchain world on how to store and retrieve data from the blockchain.
|
||||
|
||||

|
||||
|
||||
Each executor in the form of Web4 or twin is compatible with IPFS.
|
||||
|
||||
Each IPFS object can be safely stored on QSSS.
|
||||
|
||||
This provides the following unique Features
|
||||
|
||||
- unbreakable storage for IPFS
|
||||
- more distribution on global scale
|
||||
- more performance for the enduser
|
16
collections/web4/executor/web4_executors.md
Normal file
@@ -0,0 +1,16 @@
|
||||
|
||||
# ThreeFold executors
|
||||
|
||||
Executors are like digital twins but they are not linked to one specific person, they are stateless and can work on our behalf for any specific usecase and/or any pre-implemented. Some would call it our approach to serverless functions.
|
||||
|
||||

|
||||
|
||||
Peer2peer is the most decentralized way to experience our digital life.
|
||||
|
||||
- all executors talk to each other over private secure links
|
||||
- there is no blockchain involved for the compute, storage & network requirements
|
||||
- each executor needs compute, network and storage resources, this is managed by L0 Validators
|
||||
- The executor (web4 or twin) is the only entity who has control over the resource it requires, its all 100% private and fully peer2peer
|
||||
|
||||
|
||||
<!-- {{#include executors_usecases.md}} -->
|