Workers, containers and durable objects project architecture
So I'm a total noob when it comes to backend / dev ops work so apologies for the dumb questions. I'm a product designer / sveltekit FE designer trying to work out complicated backend stuff for a project I'm building. 
Sooo.. first some context..
1. I want to build a WAV to MP3 convertor that also outputs waveform data in JSON format.
2. I've built a hono app and deployed it to cloudflare workers that deals with the multipart uploads of WAV files and stores them in an R2 bucket. This all works great so far!
3. I'd like a micro-service to get triggered that then takes those WAV files, adds them to a queue, converts them to MP3s, creates a waveform JSON file and saves both of them to different R2 buckets. A plus would be to send the progress of the conversion back to the front end via a svelte store.
So my questions is, am I correct in thinking that I need to create a hono worker, that uses cloudflare queues to queue the WAV files, spin up a cloudflare container via the worker, which would be wrapped inside a durable object, get ffmpeg to convert the WAV files and generate the JSON, save those files to R2... or is that the totally incorrect way to approach it ?
I'm a total newbie to docker and containers so its all a bit overwhelming to me atm, however i'm learning! any help and guidance would be greatly appreciated!
Sooo.. first some context..
1. I want to build a WAV to MP3 convertor that also outputs waveform data in JSON format.
2. I've built a hono app and deployed it to cloudflare workers that deals with the multipart uploads of WAV files and stores them in an R2 bucket. This all works great so far!
3. I'd like a micro-service to get triggered that then takes those WAV files, adds them to a queue, converts them to MP3s, creates a waveform JSON file and saves both of them to different R2 buckets. A plus would be to send the progress of the conversion back to the front end via a svelte store.
So my questions is, am I correct in thinking that I need to create a hono worker, that uses cloudflare queues to queue the WAV files, spin up a cloudflare container via the worker, which would be wrapped inside a durable object, get ffmpeg to convert the WAV files and generate the JSON, save those files to R2... or is that the totally incorrect way to approach it ?
I'm a total newbie to docker and containers so its all a bit overwhelming to me atm, however i'm learning! any help and guidance would be greatly appreciated!
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
86,942Members
Resources
Similar Threads
Was this page helpful?
