We are currently working on a project to create a program that converts video files.
The most worrying part of the process is the aws loading part.
I received the video file that I plan to convert to files from the user (from html to formdata)
Load the video file to be converted into s3 and
Bring the loaded video file back to the server, convert it, and return it to the user (in html)
It's a structure. Using s3 to handle file programs is more important than using ec2
It's better for charging and efficiency, and it seems to be very inefficient somewhere.
I wonder if it is better to save the file directly in the directory within the web framework than to raise and lower it on s3. (The saved pre-conversion file and the converted file that is passed to the user will be deleted after delivery.)
aws ec2 django
I wrote it to ask questions well.
If you are going to use aws, you need to learn aws in advance.
If you look at the services of aws, they are divided into serverless services that do not need to be managed and services that need to be managed.
If you think about s3 and ebbs, s3 manages everything on its own without considering disk full and availability. Simply load and delete files right away. But Ebbs isn't. The capacity and performance are all different, and since it is an ebs service that depends on ec2, you have to manage ec2 as well.
In addition, s3 is the most commonly used storage in aws. If s3 is used as a file storage, it is easy to link with other aws. However, if you go to ebbs, it inevitably becomes a dependency on ec2, and the cost of s3 is also the cheapest for capacity. There are many options, and glasier or s3 is replicated in three places, and if it's not important data, you can use it without replication to reduce costs.
However, if iops is important, you should select ebs. The better the performance, the more expensive it is.
In other words, it is not easy to answer s3 vs. sebs just by asking questions. Users need objective indicators such as how much and how much tps are generated and what purpose is used to make a decision.
What are you talking about it's so efficient It's hard to answer.
If you want to operate it at the lowest price and cover many users in the future, it is composed of serverless services.
You can build web services that are affordable and scalable for your questioning requirements with four services: lambda, apigateway, s3, and cloudfront.
For the db portion, you can select dynamicodb if document db(nosql) is required, and Aurora serverless if rdb is required.
You do not need to explicitly manage them because they are all serverless.
© 2024 OneMinuteCode. All rights reserved.