{"id":2411,"date":"2020-01-10T12:14:49","date_gmt":"2020-01-10T11:14:49","guid":{"rendered":"https:\/\/www.codemotion.com\/magazine\/uncategorized\/machine-learning-as-a-service-serving-reusable-ml-models\/"},"modified":"2021-12-23T12:59:19","modified_gmt":"2021-12-23T11:59:19","slug":"machine-learning-as-a-service-serving-reusable-ml-models","status":"publish","type":"post","link":"https:\/\/www.codemotion.com\/magazine\/ai-ml\/machine-learning\/machine-learning-as-a-service-serving-reusable-ml-models\/","title":{"rendered":"Machine learning as a service \u2013 serving reusable ML models"},"content":{"rendered":"\n

Artificial intelligence<\/span> and machine learning<\/span> are huge topics at the moment. So, when I saw the title of this talk at Codemotion Amsterdam 2019<\/strong> I was intrigued. The talk was given by three developers<\/span> from ING, who build components for the rest of the business. Read on to find out how they managed to create a solution that can efficiently serve ML models across multiple teams.<\/p>\n\n\n\n

\"\"\/
ING developers<\/span> Effi Bennekers, Pierre Venter and Marcin Pakulnicki<\/figcaption><\/figure><\/div>\n\n\n\n

Effi Bennekers, Pierre Venter and Marcin Pakulnicki work as developers<\/span> in ING\u2019s Omnichannel and DevOps teams, providing tools and services for other teams to use. Many teams at ING now use machine learning<\/span> (ML) models. But generally, the teams have worked in isolation from each other. Each team researches ML, locates a suitable model from an external source, trains it with their data and then uses it. But this is a bad idea because teams keep reinventing the wheel. So the challenge was to create a system that allowed teams to share their trained models.<\/p>\n\n\n\n

Autonomy equals anarchy?<\/h2>\n\n\n\n

At ING, development teams have a lot of autonomy. This means they are free to choose what technology to use and to find their own solutions to problems. Over recent years, a trend has developed. Teams identify a problem that can be solved by machine learning<\/span>. They do some research and choose a well-known ML library. They then source their own data and train a model. This model is then pushed to their repo and packaged into the source code.<\/p>\n\n\n\n

So, what\u2019s the problem, you might ask? Well firstly, ING teams have high churn. So, the next time the team sees an identical problem they go through the whole process again from scratch. Secondly, because models are being baked into production code, they can\u2019t be updated when the data changes. Thirdly, there is little or no knowledge transfer between teams. This leads to wasted effort. Finally, all too often the models end up getting lost and have to be recreated from scratch.<\/p>\n\n\n\n

Scaling is sensible<\/h2>\n\n\n\n

The solution was to build a system that can serve multiple models from a central repository. These models can be version-controlled and can be reused by multiple teams. The models should be accessible via APIs<\/span> as shown below.<\/p>\n\n\n\n

\"\"\/<\/figure><\/div>\n\n\n\n

Automatic classification of feedback<\/h2>\n\n\n\n

As an illustration, the speakers showed how to improve the process<\/span> for classifying<\/span> user feedback. This user feedback comes from multiple sources such as reviews, Twitter, direct communications, etc. It needs to be properly categorised so that the appropriate team can action it. The old-fashioned approach involved employing people to classify<\/span> all the feedback. Feedback was captured in a spreadsheet and then manually assigned to one of 52 very specific categories. Needless to say, that process<\/span> was not very quick and gave rise to an internal saying \u201cBanking in the rearview mirror\u201d.<\/p>\n\n\n\n

The aim was to create a system that was able to classify<\/span> the feedback much faster. In turn, this would allow the relevant team to identify the problem and code a new feature for production. The solution was clearly to develop a machine learning<\/span> system that can do this classification<\/span> automatically. But this service has to be available to every team across the company. So, they came up with \u201cThe Voice\u201d. This is a web app<\/span> that can be used to classify<\/span> any feedback by clustering and labelling it.<\/p>\n\n\n\n

The Voice is effectively classifying<\/span> user feedback using ML as a service. It receives input from users of the app<\/span>. It then performs an ML\/rules-based analysis. Then the feedback is immediately passed to the responsible team.<\/p>\n\n\n\n

Data labelling and model training<\/h2>\n\n\n\n

As with all categorisation problems in ML, there are two distinct stages. Firstly, you need to label the data. Then you need to classify<\/span> it.<\/p>\n\n\n\n

\"\"\/<\/figure><\/div>\n\n\n\n

The team knew they had unlabelled data to start with, but because they knew the number of categories they could easily use KMeans clustering<\/strong> to label the data. Having labelled the data, they could then classify<\/span> it. Because of the relatively low sample count they used the SDG classifier<\/span><\/strong>. They then demonstrated how they can use this model for live feedback.<\/p>\n\n\n\n

Containerising ML models<\/h2>\n\n\n\n

The next challenge is how to package a model like this so that it can be served via a suitable platform. Importantly, the actual training of the model is out of scope. The answer is to use Docker<\/a><\/u> to containerise the models. They also needed to be able to serve multiple versions of the same model (e.g. for A\/B testing). This needed them to use GRPC for routing. The initial version<\/span> of the architecture used a combination of Docker<\/span>, zookeeper<\/a><\/u>, Kafka<\/a><\/u> and a custom-built ML platform app<\/span>.<\/p>\n\n\n\n

The initial architecture worked well. But because ING is a bank there are regulatory compliance issues that need to be addressed. They also had to be able to scale and prevent this system from being a single source of failure. The solution to that was to containerise the whole system, packaging just the relevant models into each container. The resulting architecture is shown below.<\/p>\n\n\n\n

\"\"\/<\/figure><\/div>\n\n\n\n

The final set of challenges were around how to make the system handle data frames (the data abstraction used by most ML libraries) and how to streamline the build\/release platform. The resulting solution uses GitLab Runner<\/a><\/u> to coordinate things. The resulting pipeline has three phases:<\/p>\n\n\n\n

\"\"\/<\/figure><\/div>\n\n\n\n

Conclusions<\/h2>\n\n\n\n

Building a system that is capable of serving ML models in a scalable manner is hard. Doing so in a tightly regulated industry like banking is even harder. But the benefits are clear. The end result is a system that can serve multiple ML models and versions<\/span> scalably, securely and efficiently. By containerising the models within a parent container, the team created a system that is robust, easy to deploy<\/span> and doesn\u2019t suffer from the curse of centralisation.<\/p>\n\n\n\n