tfgrid/info_tfgrid
33
3
Fork 0
Code Issues Pull Requests 2 Packages Projects Releases Activity

s

Browse Source
This commit is contained in:
kristof de spiegeleer
2024-05-23 11:09:37 +03:00
parent 2d41a9a8a2
commit 00f1b87efa
115 changed files with 333 additions and 715 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
collections/faq/faq.md
View File

@@ -888,7 +888,7 @@ The ThreeFold Grid is basically agnostic when it comes to how you structure your
If you want to put all your storage and compute on one node and lose everything if it goes down, you can do so.
If you want a highly distributed and fault tolerant system with high availability where data is never lost, you can also do so. You could build an architecture with single nodes running single workloads as the building blocks.
If you want a highly distributed and fault tolerant system with high availability where data is never lost, you can also do so. You could build an architecture with single nodes running single workloads as the building slice.
Containerized micro service architectures running on e.g. Kubernetes are basically the way that compute is being "sharded" already in the mainstream of IT, especially at large scales. Such applications fit well on the ThreeFold Grid today, since they account for the possibility that individual nodes may fail. However, many applications aren't built this way and it takes work to adapt them.