Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature request: Move Tar and Zip middlewares to Fargate #4

Open
HQarroum opened this issue Jan 23, 2024 · 0 comments
Open

Feature request: Move Tar and Zip middlewares to Fargate #4

HQarroum opened this issue Jan 23, 2024 · 0 comments
Assignees
@HQarroum
Labels
enhancement New feature or request existing-middleware A label associated with an existing middleware. help wanted Extra attention is needed triage

Comments

@HQarroum
Copy link
Contributor

Use case

The Tar and the Zip inflate middleware are based on Lambda with a maximum execution time of 15 minutes. It would be better and more scalable for customers to move the implementation from Lambda to Fargate, ensuring that very large archives can be inflated.

Solution/User Experience

Moving to Fargate in order to benefit from a longer time to inflate archives.

Alternative solutions

No response
@HQarroum HQarroum added enhancement New feature or request help wanted Extra attention is needed triage existing-middleware A label associated with an existing middleware. labels Jan 23, 2024
@HQarroum HQarroum self-assigned this Jan 23, 2024
@HQarroum HQarroum moved this to Backlog in Project Lakechain Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@HQarroum HQarroum

Labels
enhancement New feature or request existing-middleware A label associated with an existing middleware. help wanted Extra attention is needed triage
Projects
Project Lakechain
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@HQarroum