Case Study Problem To provide a high quality of service to advertisers on MDLinx with a minimum of bot traffic, for several years M3 used a bot mitigation solution. Prior to switching to PerimeterX, M3 used a solution with a reverse-proxy-based architecture, meaning that all traffic initially passed through the third-party platform. Recently, to adapt to the changing needs of the business, M3’s engineering team has begun migrating MDLinx from the existing, monolithic system to a new, redesigned system with a microservices architecture. This change was designed to improve the development process and performance while saving internal resources. M3’s existing reverse-proxy based bot mitigation solution increased latency without providing granular access to log data or control over the

Join for free to read