Long time no see. Spent more time on the backend and just recently have to back to MODX when I had the opportunity to develop media repository website for video and audio.
I firmly chose MODX. Obviously. Even though it meant my teammates had to learn something new.
Today, websites are getting bigger and bigger , faster and faster, but also centralized. Single Sign On (SSO) has become common, also AWS or R2 for big storage. Webserver no longer isolated, but just a node in many node of company network. Interconnections are getting wider, and the world is getting smaller.
Interesting to hear your experience, Lokamaya. The landscape has indeed shifted a lot; SSO, cloud storage, and distributed systems are almost expected now. I’ve been exploring similar setups myself, and it’s always a balance between flexibility and keeping things manageable for the team. Curious, how are you handling media delivery and access control in your MODX setup?
The challenge for video delivery is providing multiple resolutions for users. We setup a server to automatically render videos stored on local NAS (mostly MP4) into different HLS resolution and automatically upload them to R2 Storage, and at the same time update MODX content via API.
If we talk about DRM (digital right management), there are three leading players that ruled the internet: Google Widevine, Apple FairPlay and Microsoft PlayReady.
Netflix made a deal with Google, Apple and Microsoft directly, they even fought over the law on DRM. And most companies use a service like Brightcove to deliver single video into three proprietary DRM formats own by those players.
So, to deliver secure and high quality video (with HLS encryption) is a quite challenging.
