Both Fiduciary Exchange and Kubernetes enables application developers to run Application Containers (e.g. docker on them.
Both run many replicas of the same application container in order to scale up application reliability and performance across multiple machines.
Disposable Nodes inside Fiduciary Exchange can be viewed loosely as Pods in Kubernetes, enabling application containers sharing common networking and storage to be ran together inside.
Kubernetes has ONE service provider processing data given to it by information owners through centralised control of the application and infrastructure.
Fiduciary Exchange has MANY information owners processing their own data by controlling the application and infrastructure independently.
As each owner only needs to manage a small part of Fiduciary Exchange that it uses, the complexity is substantially reduced.
Kubernetes does not handle much outside of containers (computing abstraction). Fiduciary Exchange covers everything with Disposable Node abstraction (from software to hardware, from support personnel to computer rooms).
All Nodes whether, physical or virtual, follow the same Modular Assist management framework.
Kubernetes is designed to be ran in a few secured and stable data centres with high quality networking. Fiduciary Exchange is designed to run across the world in almost anywhere with common internet access.
Kubernetes has numerous volume types and provisioning methods.
Fiduciary Exchange only has one type (Infinite Disk) that looks and performs like a local disk to support any applications (including emails, documents, videos, databases, search engines etc.)
Kubernetes networking focuses on handling incoming traffic to services provided by the pod (e.g. kube-proxy).
Fiduciary Exchange has Network Nodes controlling both incoming and outgoing traffic from Application Nodes, Station Nodes and Room Nodes.