NetEnt: Betting on DevOps
See how a gaming company dramatically boosted deployment efficiency by adopting an ops-first DevOps approach, with talks from DOES 2017.
Join the DZone community and get the full member experience.Join For Free
how an online gaming company leveraged devops for a 4,000% increase in deployment efficiency
according to a recent report from statista, in the last 7 years, online gaming has grown from a $22b industry to over $50b annually, fueled primarily by net-based casino games like roulette, slots, and poker.
behind the scenes of over 200 of the world’s most prominent online gaming sites is a company called netent . netent (nasdaq omx net-b) is a pioneer in online gaming, entertaining the world for the past 20 years. the company’s innovative platform provides premium online and mobile gaming solutions to some of the world’s largest online casino operators in over 40 countries , handling more 110 million gaming transactions on a daily basis – roughly 16x more throughput than that of the new york stock exchange!
check out this short intro video to learn more about netent:
gaming is big business
online and mobile gaming is booming. with millions of daily active users across the globe, on multiple devices (using mobile, laptops, tablets), and thousands of addictive gaming apps – gaming is big business.
customers are invested in these applications- in making it to the next level, solving the puzzle, beating their friends, and – in the case of casino games – also winning some $$!
gaming apps have to continue to get better and better, load faster, be more entertaining, more secure, and – of course – be available 24/7/365 for players around the world, and for the businesses who rely on them.
as netent saw incredible growth, their it operations experienced a few challenges.
with hundreds of online gaming portals reliant on netent’s technology, the backend of their systems became more complex and the production footprint grew considerably. the netent application is a typical java app – with a clustered application server, database for transactions and reporting, and so on. each customer running their own casino brand also had their own test environment and supporting services. as the systems had to scale to service the growing number of customers white-labeling netent’s technology, the development and it operations that were supporting these customers became slower and more fragile.
the dev organization was creating strains on the ops teams, who were having difficulties keeping up with the pace of updates produced. as the number of games and operators in netent’s portfolio grew, they had to rethink their delivery pipeline to allow them to accelerate their releases as well as scale their operations to support the increased load and complexity.
in their delivery pipeline, deployments, in particular, became the achilles heel of the operation. a full-time employee was required to handle each and every deployment for every code change on every node in the growing production footprint. this wasn’t just for major releases – but also for bug fixes, security patches, and minor updates. the manual process took about 4 hours per deploy, and involved a 40-step checklist, often requiring downtime of the application. there was tons of risk with each deployment and downtime meant unsatisfied customers and lost revenue.
these slow, brittle, manual, error-prone deployments meant new features that were developed were taking longer and longer to actually be released into the market, and that on-boarding of new customers and applications were greatly delayed as well. the process of seeing dev work actually getting delivered into the hands of end-users became risky and unpredictable. for example, looking at the jira tickets the ops team was spending their time on – only 12% was being spent on “revenue generating” activities- such as releasing new games or onboarding new customers. majority of the time – 88% – was spent on deploying bug fixes and patches.
how do we scale?
yes. it was a pain. but, more crucially, it was a pain that can only be alleviated by throwing more people at the problem, the only way to really scale was by hiring more people, to do more manual processes, that became more and more complex. it came to be that over 17 full-time employees ended up doing deployments pretty much around the clock, just to keep the business running.
the model, simply, was not sustainable for the long term. netent was feeling the pain – and that was under ‘normal’ operations. but what if something happened??
and then – it did…
the “big bang” compelling event: netent at a crossroads
with no sign of slowing growth, and with a difficult and labor-intensive deployment process, netent found themselves at a crossroads. the world of online gaming is highly regulated and being in compliance is incredibly important – both for keeping the lights on for generating new business. netent found themselves needing to deploy a compliance fix across 70% of their customer base in order to meet new regulatory requirements. there was simply no way to cope with this volume of work with the current processes.
a task force was created, with 10 engineers who were re-assigned to be dedicated to the compliance deployments. this team spent the better part of a year and a half (4 days a week, 4 hours a day) rolling out the crucial compliance fix across thousands of servers across all customers. ultimately, the team accomplished the task. but at what cost? at what loss of productivity? to innovation? to employee satisfaction and retention?
netent realized they needed to make a change. from this compliance ‘big bang’, came a new realization, unleashing a new era for netent’s delivery practices.
an ops-first approach to devops
at devops enterprise summit san francisco 2017 , aloisio rocha, agile product owner at netent, described the organization’s challenging, but successful journey to devops and automation.
netent realized that the next time a change of this scale needed to happen, they might not have the time or the resources to make it happen – and they understood the devastating impact this could have on their business. netent announced “ project time to market (ttm) ” – taking an “ops-first” approach to their devops transformation. this cross-functional team has set an aggressive goal for the company: cutting deployment time of new apps over the whole customer base to under 2 weeks , as well as accelerating and streamlining the onboarding of new customers. and they wanted to do it all in less than a year.
aggressive, for sure. but as you’ll see, they ended up doing even better than they expected!
the main focus of the ttm initiative was around automation. the team, having documented their delivery process and value stream on a whiteboard, put their minds together to see what the most time-intensive actions were, and where they could use automation to accelerate the most crucial bottlenecks in their pipeline. naturally, they chose to focus on deployments, to start with. not only is this the most critical process on the ops side (finally delivering new code to end users) and that has the greatest impact on the business, but – as we’ve seen from the state of the devops reports – deployment success is the best indicator for devops success.
“we also wanted to remove any technical impediments. so we took those deployment checklists, and automated them at every step- crossing them off as we went,” said rocha. “we took all our decision and approval gates and automated them as well. so, no more dependencies on other teams or manual steps in the process.” a self-service catalog of vetted pipelines and deployment processes allowed team members to easily reuse these automation pieces- ensuring they are the most recent process and configuration, that they are in compliance, and that they do not need to re-invent the wheel to onboard or support new customers or variants of the applications.
after going through the value stream mapping exercise and white-boarding their deployment processes, netent chose electricflow from electric cloud to model the deployment and release pipelines and to orchestrate all of the point-tools, scripts, configurations, and environments involved in the software delivery process under one platform.
this not only allows for automating the entire pipeline, but also increases visibility while maintaining compliance and control. netent was able to put an end to “throw-over-the-wall” or manual handoffs between steps in the pipelines or between different operations or tools, and create a fully-automated process with shared visibility to all stakeholders. this helped not only with velocity and speed, but with compliance and auditability requirements as well.
the results have been staggering and enabled netent to release better products faster.
- for their engineers, what used to take 2 to 4 hours to deploy now takes less than 15 minutes.
- from 1 deployment per month per engineer, the team now does more than 40 deployments/engineer.
- the 30 to 40 step checklists have been eliminated , replaced by a streamlined and automated series of tasks that happens nearly instantaneously.
- the team of 10 dedicated to a large-scale deployment for 18 months is gone – with that brain-power now re-deployed to more meaningful tasks than copy-pasting run books’ tasks. the same volume of work that previously took 1.5 years is now accomplished by a team of just two people, in less than 2 weeks .
- overall, deployment efficiency has grown by 4000%. the increased efficiency and frequency of deployments has led to faster and more reliable releases, and to an overall better product experience and more satisfied customers.
“one of the benefits we have seen from using electricflow is the whole process is now automated and repeatable. we’re scaling by automation , not by adding more people to our team,” said rocha. “the whole process is visible to us. we have traceability and are compliant. we’re actually spending our time on creating business advantage instead of sitting around copy-pasting all day. and we have achieved time-to-market for our platform.”
ultimately, netent has enjoyed incredible success because of their quality of products, innovative and creative vision, and dedication. thanks to their foresight and commitment to staying on the cutting edge, netent has now baked automation and devops into their development processes, positioning the company at an incredible competitive advantage as they continue to lead the future of online gaming.
netent shows that when you bet on devops, red (dev) and black (ops) both win, and – of course – the house!
to learn more about the netent’s devops journey, check out the video of aloisio’s talk at the recent devops enterprise summit:
Published at DZone with permission of Anders Wallgren, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.