awesome done Abdullah Abdulfatah

Abdullah Abdulfatah Is it meant to be hosted somewhere? Cos I added link to YouTube video but failed to work. Thanks

Taiwo Hassan Yusuf Alright then, awesome 🙌

Thanks Taiwo Hassan Yusuf I didn't even notice the colour coding, thanks for expanding on that, that's another tip to add to what I learned from this article. Still wondering why every request passes through the FFMBPROBE when some could already be cached and mapped url-uuid-result

Hi Taiwo, thanks for the amazing article, particularly learned something new from the socketIO section, your explanation of how it was work was brilliant. As for Durator , it didn't work for me, it asked for a link to any media file and I put a youtube link but Generate button wouldn't click; As for metaworka , I uploaded a png thumbnail file but got a response that it was a video and the frame rate was 25 fps. I also have a question about the diagram under caching for speed section: why is cache a separate block when it is actually been handled by the same Redis, you mentioned that you map the URL to a UUID and to the result , shouldn't it go to Redis straight, get processed by FFPROBE and return back to Redis cos the cache looks like a separate entity something like this

Taiwo Hassan Yusuf Got it!

Nice article Taiwo, thanks for sharing. This however begs the question why do you want to encrypt your jwt since at the end of the day, you're sending it to the Frontend (unless it's for server to server communication). One major catch for jwt is do they can be decrypted on the client side and the data displayed to the user or used for some basic controls. When you encrypt that, you will have to share the encryption key with the frontend which makes it unsafe anymore. What is your thought on this?

Good intro Azeez, thanks for sharing