SOLUTIONS / MEDIA
Uploading a source file, processing it and making it available consume different resources. Separate those steps when designing media infrastructure with FibaCloud products. Assess compute, storage organization, permissions and data transfer against the way your content workflow actually operates.
01 / Overview
Originals, edited outputs, previews and archive copies serve different purposes. They may not need identical access and retention rules. Consider file size, reprocessing needs and access frequency as well as the number of files.
Treat video conversion, image processing and publishing as separate workloads. File storage alone is not a live streaming, CDN or media processing product. Choose the necessary software and distribution components separately.
Consider taking intensive conversion work out of user requests. Queues, retries and output validation belong in the application design.
Classify sources, outputs and archives by purpose. Distinguish reproducible derivatives from irreplaceable originals before defining deletion policies.
Identify who downloads files, how often and through which path. Transfer costs and permissions matter alongside storage capacity.
02 / Architecture
Example workflow: source files, processing, publication and archives are separate steps. Included CDN, live streaming or processing software is not assumed.
Selection guide03 / Selection guide
| Consider | How to decide | Why it matters |
|---|---|---|
| File lifecycle | Set retention for sources, derivatives and archives. | Unnecessary duplication and accidental deletion become easier to assess. |
| Processing capacity | Measure jobs with representative formats and quality settings. | Sizing reflects the actual conversion workload. |
| Access model | Separate private files, public outputs and controlled sharing. | Access requirements are addressed in the application design. |
| Data transfer | Estimate uploads, downloads and external-service traffic. | Cost planning extends beyond stored gigabytes. |
04 / Use cases
Measure processing time, CPU, memory and temporary disk use. File size alone does not explain conversion cost.
Assess content management, file access and user requests together. Verify caching and distribution capabilities in the components you choose.
Define ownership, versions and retention for originals. Test retrieval even when archive access is infrequent.
05 / From planning to operation
Record formats, sizes and ownership. Prioritize protection for sources that cannot be recreated.
Plan temporary files, queues and output checks. Define cleanup and retries for failed jobs.
Test private and shared files with different users. Knowing a file name should not substitute for authorization.
Reassess unused outputs and archive needs regularly. Check source and backup relationships before deleting content.
They are different components. Object storage holds files; a CDN provides a distribution and caching layer. Do not assume CDN functionality is included without verifying the service scope.
Formats, codecs, quality, concurrent jobs and software determine the workload. Measure CPU, memory and disk use with representative files before choosing.
Not necessarily. The same permissions or deletion operation may affect both copies. Assess the need for independent recovery separately.
Decide whether a file is public or restricted. Implement identity, permissions and link lifetime using your software and verified storage capabilities.
Connect product decisions with installation, configuration and operating knowledge.
These references explain the technical concepts discussed on this page. Available configurations and service scope are defined by FibaCloud product and order information.
FIBACLOUD / Media
Tell us about your application, expected usage and operating requirements. Let’s bring the resource choices together.
