Skip to content
This repository has been archived by the owner on May 30, 2023. It is now read-only.

Implement AWS Fargate #6

Open
pcaversaccio opened this issue Feb 3, 2022 · 4 comments
Open

Implement AWS Fargate #6

pcaversaccio opened this issue Feb 3, 2022 · 4 comments
Assignees
Labels
backend 🏭 Issues related to back-end feature 💥 New feature or request

Comments

@pcaversaccio
Copy link
Member

As part of the architecture refactorisation, we should start using AWS Fargate. If we use a serverless, pay-as-you-go compute engine we can optimise memory management as well as our cost strategy.

@pcaversaccio pcaversaccio added feature 💥 New feature or request backend 🏭 Issues related to back-end labels Feb 3, 2022
@ttattl
Copy link
Collaborator

ttattl commented Feb 22, 2022

Currently, AWS Fargate does not support GPU (CPU is ok).
aws/containers-roadmap#88
https://aws.amazon.com/blogs/architecture/building-real-time-ai-with-aws-fargate/
I think we can keep our structure until we get full support from Fargate. We can see some recommendations in Git but basically, it looks the same with us right now. So, let's wait for the full version of AWS.
@giaoNguyen70 and @pcaversaccio how do you think ?

@pcaversaccio
Copy link
Member Author

Hmm but wouldn't be Fargate an improvement for our EC2 CPU instance management still? I agree on the GPU part and we can wait for that but AWS Fargate could be also relevant for the other non-GPU-related processing.

@pcaversaccio pcaversaccio transferred this issue from another repository Feb 23, 2022
@ttattl ttattl self-assigned this Mar 2, 2022
@ttattl
Copy link
Collaborator

ttattl commented Mar 2, 2022

I am considering keeping the current flow or changing to Fargate. Currently, our flow also works similarly to Fargate, and also can support GPU if we need it. If we change now I am not sure about GPU.

@pcaversaccio
Copy link
Member Author

Let's re-evaluate the AWS Fargate issue (in particularly re GPUs) in the next phase again (i.e. May 2022). However, for the moment we go with our existing, custom-built architecture.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backend 🏭 Issues related to back-end feature 💥 New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants