With the increased load on our services, we had to address different aspects of scaling our services, from splitting the codebase into a microservices based architecture, to migrating and consolidating our legacy cloud infrastructure. Like many other successful software products, we started out with a monolith system, all the logic for handling publishers, advertisers, as well as the ads delivery itself was in the same codebase. The above slide shows the growth in traffic, and how we from engineering have introduced architectural changes to allow our system to scale accordingly. This helps advertisers reach the intended audience and publishers to receive higher ad revenue in their games. Over the last four years, the number of ads shown per week in mobile games integrating our Unity Ads Monetization SDK has increased from 250 million views per week to 2.5 billion views per week.įor an ad platform like Unity Ads, the amount and quality of data we have access to improves our ability to show relevant ads to users.

Our mission at Unity is to help you become successful with your games, whether you’re a publisher who’s building a business around games through monetization with ads, or an advertiser aiming to acquire new users. Video from the presentation is available here: DEVOPS 2018 - Unity Technologies Keynote, Day 2 This blog post follows up on our talk with more details on the topic, and some general advice for similar big projects.

As Unity Ads engineering team, we got invited to the DEVOPS 2018 conference in Helsinki in December 2018, to present how we have approached the challenge of scaling up our systems to handle a 10x increase in load over a period of four years.Īmong other things, we discussed what we learned from our first incomplete migration attempt and how we applied that knowledge when successfully migrating our large-scale infrastructure to the Google Cloud platform.

Unity cloud build sloqw