D-Terminator

    D-Terminator   

   High-Performance Peer-to-Peer Connectivity to vSoC Decenter Cloud_  

[ TYPE : Power Modules ] 

░█ D-Terminator : Decenter Terminator [ pronounced: "Determinator" ]

The Decenter Terminator [D-Terminator] Syborg "Determines" + "Terminates" various kinds of network connections To and From the vSoC Decenter [ Decentralized vSoC Sites ].

There are various D-Terminator Power Modules that focus on different types of network connectivities. 

Each D-Terminator Power Module can be run in one SoC or separately in many SoCs depending on the bandwidth and CPU requirements. D-Terminator can be scaled by simply adding more SoCs and running the required D-Terminator Power Modules on them. 

Practically all D-Terminator Power Modules can transparently modify all their critical networking configurations, traffic flows and related aspects in realtime without bringing down or affecting the existing network connections, allowing for seamless management and scaling.

D-Terminator gives the vSoC Decenter Provider the best flexibility unseen in the industry today by giving them an opportunity whereby they are allowed to be connected to a "MIX" of Cable, DSL, Fibre, Satellite, Wireless and other Modems & Routers from various Internet, Broadband, Wireless & Satellite Providers in a parallel manner.

This allows for provisioning of a mix of networks to the Tenants depending on their cost and performance requirements. This unique leverage allows the vSoC Decenter Providers to additionally profit substantially on top of the provisioning of the Decenter Cloud to their customers.

D-Terminator transparently works by integrating different Public IPv4 IP addresses from different providers.

Fibre -----------| S |
DSL -------------| W |
Cable -----------| I |====|[ _D-Terminator_ ]|===[ .vSoC DECENTER CLOUD. ]
Satellite -------| T |    |[  _D-Switch:R_  ]|
Wireless --------| C |
Others ----------| H |

Below are some of the D-Terminator Power Modules:

░█ D-Terminator-0 ◂[๏∵๏]▸

D-Terminator-0 allows outgoing connections from Virtual Machines across different Spatial Clusters of the Tenants to access the Internet. 

For example, Virtual Machines and Container Technologies [ Docker, LXC, Kubernetes. etc ] running inside them get transparent Internet connectivity.

░█ D-Terminator-1 ◂[๏∵๏]▸

D-TERMINATOR-1 allows incoming connections from the Internet onto their designated destination Virtual Machines across various Spatial Clusters.

The top highlight benefit of D-TERMINATOR-1 is that it conserves Public IPv4 addresses. 

An example of the conservation aspect of IPv4 is as follows: For example, if one Public IPv4 address "A" is used for one application [eg. web hosting, database etc], then with D-TERMINATOR-1, the same one Public IPv4 address "A" can be equivalent to about 50,000 IPv4 Public Addresses due the manner in which the D-Terminator-1 Syborg spans out that one Public IP amongst different destination Virtual Machines across various Tenant Spatial Clusters.

D-Terminator-1 transports all incoming traffic coming to its specfic Public IP address and port to its designated destination-specific IP address and port of the Virtual Machine within the required Tenant Spatial Cluster. It works with any Layer 3 UDP or TCP.

Usage Examples:

- Website Hosting - Keep the regular webserver [Apache, NGINX etc], LAMP stack, etc. in a virtual machine in the vSoC Decenter Cloud. Change the Domain Name's DNS IP address to reflect the Public IP:Port designated by D-Terminator-1, and now you are hosted within your Spatial Cluster in the vSoC Decenter Cloud. 

- OR - Simply proxy forward your Domain Name or send a 301/302 redirect to the  IP:Port designated by D-Terminator-1.

- Keep practically any application that can be accessed over Layer 3 within the vSoC Decenter Cloud, and access whole or parts of it via the Public IP:Port designated by D-Terminator-1 [ or via a Domain Name pointed to the Public IP:Port designated by D-Terminator-1 ].
    
░█ D-Terminator-2 ◂[๏∵๏]▸

D-Terminator-2 allows for the Decentralized Ad-Hoc, Peer-to-Peer, LAYER 2 with Integrated VLAN Inter-Connectivity of the local and/or global vSoC Decenter Sites.

All the Spatial Clusters have transparent Layer 2 connectivity and access across all vSoC Decenter Sites, as their designated VLANs span all the vSoC Decenter Sites. 

░ Below is an example of a vSoC Decenter Cloud:

▸ vSoC Decenter Sites : 200

▸ Number of SoCs per site : 50 [ with 800 CPU cores/threads running at ~ 5.2 GHz to 5.4 GHz ].

▸ Total 160,000 cores/threads across 200 sites.

☼ If a Tenant "A" had VLAN 1000 designated to its Spatial Cluster, and Tenant "A" had a varying number of Virtual Machines across 50 sites, then all those Virtual Machines of Tenant "A" will have automatic transparent Layer 2 inter-connectivity. ☼

☼ Tenant "A" can control all their Virtual Machines and all the related aspects by logging into just one vSoC [or as many as they want]. ☼

░█ D-Terminator-3 ◂[๏∵๏]▸ 

D-Terminator-3 allows for the transparent Layer 2 or Layer 3 Interconnection of the vSoC Decenter Sites with Tenants' Data Center[s] and Corporate LAN[s].

Tenants connecting to D-Terminator-3 at different Decenter sites can have multiple, shortest path access to their virtual machines while having link redundancy at the same time. 

░█ D-Terminator-4 ◂[๏∵๏]▸ 

D-Terminator-4 allows for the accessing of Space-Age Management Interfaces of the vSoCs across the Decenter from the specific designated IP range assigned to the Tenant.
SynchroKnot Limited, Hong Kong, SAR of China [ website - content ] by SynchroKnot is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.
Based on a work by its creator Mehul Sharma at SynchroKnot Limited, Hong Kong, SAR of China : synchroknot.[com|cloud|org].