In the system we built, some content was live, some was VOD, some was covered by subscription, some could be purchased individually, some was free (sponsored by

In the system we built, some content was live, some was VOD, some was covered by subscription, some could be purchased individually, some was free (sponsored by a patron org that needed attribution), some was available all year round and some only for a very limited period. On top of that we supported purchases/subscriptions on every major mobile/TV platform and then some - all shared, so when you paid on AppleTV, you could watch it on the web, etc. This included working around platform-specific brain damage, e.g. on Amazon FireTV you can only offer VOD content purchases through Amazon's own catalogue. This also included interoperating with local vendors running the most oddball systems you'd ever witness. Because of this complexity (which "only" reflected real-world streaming rights deals), we needed a hero UX designer and tight collaboration between frontend, backend, video, and design teams. Forget devops, we have VideoOps. If you think you can draft a standard that covers each and every possible case, I will happily rate it - the measurement unit is blood sweat and tears. If it gets a 10/10, I will personally rewrite every part of our system to comply - no joking.