Data plane
In distributed systems, the component responsible for handling actual data storage, retrieval, and movement; in HTC Grid, stores task data that workers access during execution
As defined in Building and Running an HPC Grid Using Cloud Native Services - Flamur Gogolli & Kirill Bogdanov
Where it comes up · 1
- Building and Running an HPC Grid Using Cloud Native Services - Flamur Gogolli & Kirill Bogdanov3 claims
Most important claims · 3 of 3Search all claims for “Data plane” →
- The same logic for choosing data plane storage applies to the compute plane: EKS or Kubernetes is perhaps the most common choice because of interoperability and ability to run on-premises and on other cloud providers, but there is no one-size-fits-all solution and the list can be extended if customers want something elseBuilding and Running an HPC Grid Using Cloud Native Services - Flamur Gogolli & Kirill Bogdanov
- When choosing a data plane (storage layer) for HTC Grid, the selection depends on customer experience and workload objectives: for time-sensitive workloads, ElastiCache provides very low latency; for cost optimization with large data volumes, S3 is the best choice; for POSIX filesystem requirements, options like FSx are availableBuilding and Running an HPC Grid Using Cloud Native Services - Flamur Gogolli & Kirill Bogdanov
- HTC Grid has three main components: a client application (REST API entry point), a control plane (fully serverless and managed services), and a compute plane (with modular variants like EC2, EKS, or Kubernetes), plus a data plane for task submission and retrievalBuilding and Running an HPC Grid Using Cloud Native Services - Flamur Gogolli & Kirill Bogdanov