I'm currently working on creating a website and I've been pondering the best way to store the files that will be uploaded to the site, such as images, videos, and audio. Initially, I considered storing them on the same server where the website will be hosted, in a cloud server.



However, the available storage is limited, expensive, and primarily intended for website hosting rather than file storage. Additionally, there are concerns that access may be restricted if there is extensive manipulation of files.

After some research, I looked into using S3 or Google Cloud, which offer large storage capacity. However, I discovered two potential issues. Firstly, they have the ability to automatically charge my card, which seems unconventional. Secondly, the problem lies in the distribution of files rather than their size. It appears that a high volume of GET requests could result in significant charges, with no apparent option to limit the number of requests. This raises the worry that I could end up owing a substantial amount of money if someone were to send a large number of GET requests to my site.

Another alternative I considered is purchasing a cheap NAS and setting it up at home to distribute the files, since the website is not expected to have a large number of visitors. However, this approach may require obtaining a static IP from the provider and could potentially involve other technical challenges.

The main question remains: where and how can I securely and affordably store media files for a website, considering the potential issues with cloud servers and the complexities of setting up a personal NAS?
And moreover, is there a way to prevent unexpected financial liabilities arising from high numbers of GET requests to the site? Any thoughts on this matter would be greatly appreciated.

One innovative approach to this challenge involves leveraging a combination of cloud storage and edge computing. By utilizing a cloud provider's scalable object storage solution, such as Amazon S3 or Google Cloud Storage, you can efficiently store and manage media files while benefiting from high availability and durability. However, to address concerns about potential costs associated with high volumes of GET requests, integrating a content delivery network (CDN) with advanced caching capabilities can help minimize the impact on expenses. A CDN can dynamically cache and serve media files closer to the end-users, reducing the load on the storage infrastructure and mitigating potential charges related to GET requests.

Furthermore, exploring decentralized storage options, such as leveraging blockchain-based storage networks, presents an intriguing possibility for cost-effective and secure file storage. These platforms offer a distributed approach to storage with built-in redundancy, potentially reducing costs compared to traditional cloud storage providers. While still an emerging technology, decentralized storage solutions provide an alternative worth considering for certain use cases.

In terms of security, it's essential to prioritize the encryption and access control features offered by any chosen storage solution. Robust encryption mechanisms and granular access controls can help safeguard the confidentiality and integrity of media files, especially if they contain sensitive or proprietary content.

For those seeking to avoid the technical challenges of setting up a personal NAS, managed hosting services that specialize in media file storage present a viable option. These providers offer tailored solutions designed specifically for storing and delivering media assets, addressing concerns related to scalability, accessibility, and cost management. By partnering with a managed hosting service, website owners can offload the complexities of managing file storage while ensuring high performance and reliability for their media content.
A comprehensive assessment of the specific website's needs, combined with a thorough evaluation of available storage options, will be key in determining the most suitable, sustainable, and cost-effective approach to securely storing media files while minimizing unexpected financial liabilities.

Serverspace offers a unique solution for handling such tasks – Object Storage.

With our service, you are charged based on the disk space utilized and outgoing traffic (the amount of data transmitted). Our storage system is compatible with Swift and S3. You can estimate the expenses using the calculator provided on the website (the costs are displayed in Belarusian rubles).

Payments are deducted from the user's personal account on Serverspace as per the usage.

The most convenient way to store files is through Telegram. With the capacity to store up to 1750 megabytes, users can easily upload files and keep them there indefinitely without any cost. I have personally tested this service and found it to be reliable for long-term file storage. Have you tried using Telegram for file storage?

The best practice is to only store path of the files in the database and be sure to correctly handle deletions or modifications to avoid orphaned files. It's a bad practice to store file in db. But instead of that, you can store the file in server disk and map the file path in db. This will be good.

Quote from: J.Bhp on Jan 07, 2024, 02:58 AMI'm currently working on creating a website and I've been pondering the best way to store the files that will be uploaded to the site, such as images, videos, and audio. Initially, I considered storing them on the same server where the website will be hosted, in a cloud server.



However, the available storage is limited, expensive, and primarily intended for website hosting rather than file storage. Additionally, there are concerns that access may be restricted if there is extensive manipulation of files.

After some research, I looked into using S3 or Google Cloud, which offer large storage capacity. However, I discovered two potential issues. Firstly, they have the ability to automatically charge my card, which seems unconventional. Secondly, the problem lies in the distribution of files rather than their size. It appears that a high volume of GET requests could result in significant charges, with no apparent option to limit the number of requests. This raises the worry that I could end up owing a substantial amount of money if someone were to send a large number of GET requests to my site.

Another alternative I considered is purchasing a cheap NAS and setting it up at home to distribute the files, since the website is not expected to have a large number of visitors. However, this approach may require obtaining a static IP from the provider and could potentially involve other technical challenges.

The main question remains: where and how can I securely and affordably store media files for a website, considering the potential issues with cloud servers and the complexities of setting up a personal NAS?
And moreover, is there a way to prevent unexpected financial liabilities arising from high numbers of GET requests to the site? Any thoughts on this matter would be greatly appreciated.

If your website experiences high traffic or has a lot of large files, it can compete for resources with your website itself. This could lead to slower website loading times or performance issues.

Content Delivery Networks (CDNs): Often integrated with cloud storage, CDNs deliver your media files from geographically distributed servers, further improving performance for global audiences.

Quote from: J.Bhp on Jan 07, 2024, 02:58 AMI'm currently working on creating a website and I've been pondering the best way to store the files that will be uploaded to the site, such as images, videos, and audio. Initially, I considered storing them on the same server where the website will be hosted, in a cloud server.



However, the available storage is limited, expensive, and primarily intended for website hosting rather than file storage. Additionally, there are concerns that access may be restricted if there is extensive manipulation of files.

After some research, I looked into using S3 or Google Cloud, which offer large storage capacity. However, I discovered two potential issues. Firstly, they have the ability to automatically charge my card, which seems unconventional. Secondly, the problem lies in the distribution of files rather than their size. It appears that a high volume of GET requests could result in significant charges, with no apparent option to limit the number of requests. This raises the worry that I could end up owing a substantial amount of money if someone were to send a large number of GET requests to my site.

Another alternative I considered is purchasing a cheap NAS and setting it up at home to distribute the files, since the website is not expected to have a large number of visitors. However, this approach may require obtaining a static IP from the provider and could potentially involve other technical challenges.

The main question remains: where and how can I securely and affordably store media files for a website, considering the potential issues with cloud servers and the complexities of setting up a personal NAS?
And moreover, is there a way to prevent unexpected financial liabilities arising from high numbers of GET requests to the site? Any thoughts on this matter would be greatly appreciated.

If your website experiences high traffic or has a large volume of files, the server might struggle to handle both web serving and file storage.

Quote from: J.Bhp on Jan 07, 2024, 02:58 AMI'm currently working on creating a website and I've been pondering the best way to store the files that will be uploaded to the site, such as images, videos, and audio. Initially, I considered storing them on the same server where the website will be hosted, in a cloud server.



However, the available storage is limited, expensive, and primarily intended for website hosting rather than file storage. Additionally, there are concerns that access may be restricted if there is extensive manipulation of files.

After some research, I looked into using S3 or Google Cloud, which offer large storage capacity. However, I discovered two potential issues. Firstly, they have the ability to automatically charge my card, which seems unconventional. Secondly, the problem lies in the distribution of files rather than their size. It appears that a high volume of GET requests could result in significant charges, with no apparent option to limit the number of requests. This raises the worry that I could end up owing a substantial amount of money if someone were to send a large number of GET requests to my site.

Another alternative I considered is purchasing a cheap NAS and setting it up at home to distribute the files, since the website is not expected to have a large number of visitors. However, this approach may require obtaining a static IP from the provider and could potentially involve other technical challenges.

The main question remains: where and how can I securely and affordably store media files for a website, considering the potential issues with cloud servers and the complexities of setting up a personal NAS?
And moreover, is there a way to prevent unexpected financial liabilities arising from high numbers of GET requests to the site? Any thoughts on this matter would be greatly appreciated.

 It's simple to manage both your website and files from one location. Uploads and downloads are often seamless.

For your website's media files, consider cloud storage services like Amazon S3, Google Cloud Storage, and Dropbox for reliable and scalable solutions. These platforms offer easy integration, high availability, and cost-effective storage options for your website's needs. Additionally, content delivery networks (CDNs) such as Cloudflare and Akamai can improve performance by caching and serving media files from servers closer to your website visitors.