Project Summary:
The Ad Engine will replace direct Ad calls to third party Ad Services from the HLS stream (injected to by Segmenter or SCTE35) to the new Ad Engine. The Ad Engine will evaluate rulesets based upon content & Ad metadata held, the decision will be made on which Pod to serve and will redirect the HLS stream to the Ad servlet to retrieve the content. The rules based Ad Engine will enable more in-house control over rulesets including a more granular approach, which in turn will enable a higher ROI from advertising via user and/or segment targeting and also commercial separation (avoidance of competing ads within the same pod or adjacent pods). The core feature of the service is to create a Smart Ad Router. Technology & Process:
We will be building an outward facing web application communicating with RESTful api written in Scala. The architecture will be a SPA using modern JavaScript framework, mostly likely Angular 4 or ReactJS possibility utilising TypeScript but input from the engineer writing the code will be needed. The engineer will have the opportunity to provide input into the design and functionality of the application, as a high level overview the application will allow users to create complex rule definitions, for Ad decisioning based on metadata held in the system.
Working with in-house Design and UX team we will creating a production-ready application, the development team are DevOps focused, with CI / CD in place from first sprint, iterative development in a scrum style process make this an exciting greenfield project
6 months +
Contact: Alex Lashford alexl@cakesolutions.net and Peter Evison petere@cakesolutions.net