Stack recommendation - Photography and Video Management
Unanswered
CarlosGarcia posted this in #help-forum
Hello everyone,
I am developing an admin dashboard for a photographer/videographer client. A core feature is allowing the client to upload and manage content for their customers, who can then view and download their purchased media via secure galleries.
The file sizes are significant, ranging from 500 KB for photos up to 5 GB for high-resolution videos.
Current Stack:
- Framework: Next.js
- Authentication: Clerk
- Database & Backend: Convex (for user/client metadata)
The Challenge:
I initially planned to use Convex for file storage. However, after reviewing the pricing model, it's clear that storing large video files directly in Convex will lead to prohibitively high costs as the client's library grows.
Proposed Solution:
I am considering a hybrid approach:
1. Use the Dropbox API exclusively for storing the large, original files.
2. Generate and store only a lightweight WebP thumbnail and the Dropbox file link in my Convex database.
Questions:
1. Has anyone implemented a similar architecture? I'm interested in feedback on its viability and potential pitfalls.
2. For those who have used the Dropbox API/SDK with Next.js, what was your experience regarding performance, developer experience, and handling authentication for secure downloads?
Thank you for any insights you can provide.
I am developing an admin dashboard for a photographer/videographer client. A core feature is allowing the client to upload and manage content for their customers, who can then view and download their purchased media via secure galleries.
The file sizes are significant, ranging from 500 KB for photos up to 5 GB for high-resolution videos.
Current Stack:
- Framework: Next.js
- Authentication: Clerk
- Database & Backend: Convex (for user/client metadata)
The Challenge:
I initially planned to use Convex for file storage. However, after reviewing the pricing model, it's clear that storing large video files directly in Convex will lead to prohibitively high costs as the client's library grows.
Proposed Solution:
I am considering a hybrid approach:
1. Use the Dropbox API exclusively for storing the large, original files.
2. Generate and store only a lightweight WebP thumbnail and the Dropbox file link in my Convex database.
Questions:
1. Has anyone implemented a similar architecture? I'm interested in feedback on its viability and potential pitfalls.
2. For those who have used the Dropbox API/SDK with Next.js, what was your experience regarding performance, developer experience, and handling authentication for secure downloads?
Thank you for any insights you can provide.