Evaluation of Serverless Solutions

openHPI / poseidon

Scalable task execution orchestrator for CodeOcean

MIT License

9 stars 1 forks source link

Evaluation of Serverless Solutions #219

Open mpass99 opened 2 years ago

mpass99 commented 2 years ago

User Story

As a DevOps
I want to use a serverless solution as execution environment In order to take advantage of benefits such as the better scalability.

Acceptance Criteria

[ ] Create or reuse requirements for the serverless jailing solution.
[ ] Evaluate suitable jailing solutions

Implementation Note

[ ] Evaluate suitable jailing solutions
- [x] List existing Cloud Services that may provide a suitable solution.
- [ ] Evaluate and filter the found solutions on a theoretical level.
- [ ] Create PoC for the remaining solutions.
- [ ] Evaluate the remaining solutions.

MrSerth commented 1 year ago

We could also think of serverless container-based solutions, such as AWS Fargate. This would also allow us to re-use the Docker images we already have for the on-premise Nomad installation.

mpass99 commented 1 year ago

What do you think of those Serverless Solutions to be evaluated?

AWS Fargate (Container-based)
Scaleway Functions (Function-based)
Scaleway Container (Container-based)
Azure Functions (Function-based)
Azure Container (Container-based)
Google Functions (Function-based)
Google Cloud Run (Container-based)

mpass99 commented 1 month ago

We already have a functioning Serverless Executor for Poseidon based on AWS Lambda Functions. However, if I remember correctly, the AWS Functions are not fully isolated. AWS prewarms and reuses functions and, therefore, allows breaching the isolation e.g. on the filesystem layer and the process layer.
This reevaluation of Serverless Solutions should be used to identify a provider allowing such isolation and still keeping the advantages identified with the AWS solution.