RTE Player tech stack

D Hayes

RTE Player gets a lot of criticism. I don't use it so can't comment.

But does anyone know what the tech stack and hosting set up is like? Live streaming and video hosting websites are a notoriously hard nut to crack in general. In terms of performance and scalability.

Usually it's a case of throwing as much hardware as you can afford at the problem. Would love to know how much is spent monthly and where it's hosted. I assume it's some sort of AWS EKS Kubernetes type effort. But maybe I'm giving them too much credit?

Atlantic Dawn

It works perfectly fine every time when using the non advert version so the issue is not bandwidth or backend related.

Talisman

The player software is an implementation of the DASH-IF client. The service also uses the Highwinds CDN.

If you're looking to implement your own service then check out GPAC, it's open source but requires a commercial license.

fritzelly

The backend uses this



Apart from that it is just a badly programmed implementation of VOD
Their solution is not scalable so do not give them any credit - any kind of live program that is even mildly popular suffers extreme lagging or just plain gives up trying to stream

Maybe if they used AWS they would have better global distribution

atilladehun

Why do they have to develop their own at all? There must be thousands of TV stations around the world. Someone must be selling a decent structure.

Then there's the dedicated streaming companies. YouTube run geoblocking, ads, playlists. They provide services for bigger companies like US TV stations and the NBA for example. Really would be less hassle I'm sure. There's got to be a few more bespoke companies offering services.

Can't understand why rte need to invent the wheel.