This article was published as a part of the Data Science Blogathon
In Real-world, machine learning is not just about making your model and achieving high accuracy, this is only a small percentage of the total machine learning project.
MLOps are the must-know skills that machine learning engineers should know about. MLOps is a process of taking your model into the production system. A vast amount of work was done in achieving model accuracy in this era. But, if you’re building your product it’s not just about models.
In this article, we will be discussing MLOps, from Scoping a problem to deployment, Monitoring, and Maintaining the system.
The way I like to define MLOps is that it’s a process for developing an end-to-end product from scoping a problem to the deployment, monitoring, and maintaining the product.
Nowadays, many companies are integrating ML into their product and the rise of MLOps has increased drastically.
Here’s the pic that you can see that there is a small percent of ml code in the whole ml product.
In the above figure, you can see that there is a small percentage of code contributed to the whole machine learning project. Below are the explanation of the important terms shown in the above picture:-
Scoping or defining a project is one of the key parts of the MLOps Architecture. In this stage, you decide on which to work on in the particular project.
Eg:- Let’s you’re building a Speech recognition system, then In that case you will tend to work on some of the key metrics such as accuracy, latency, etc.
Eg:- Let’s say you’re working on an image recognition system, then In that case you will tend to more work on some of the key metrics like Image preprocessing, normalizing and etc.
The main problem that machine learning engineers fail because they don’t understand the problem statement and they haven’t scoped the problem. So I recommend spending some amount of time on this also with your team.
Tip:- Whenever you’re working on this stage, try to discuss the things with your team on giving priority to the metrics.
In this stage, you’ll define data and establish the baseline and you’ll work on labeling and organizing the data.
Eg:- Let’s say you’re working with audio data, for example, you will normalize the volume of the audio and do some more preparation of the data.
Eg:- Let’s say you’re working on image data, you’ll normalize your image, crop your image, resizing and etc.
The challenge you might face is that your data is in very bad condition, I recommend trying to label or organize the data manually.
Tip:- Before preparation Try to do the data analysis to get a better sense of the data, you’re working on.
In this stage, you’ll work on making your model, which includes Research and Algorithm and Hyperparameter tuning to make your model work.
Here, you select and train the model and perform some error analysis and try to improve the performance with the help of error analysis.
In this stage the challenge you might face challenges like Hyperparameter tuning and selecting the best algorithm.
Tip:- Whenever you’re struggling in selecting the best hyperparameter, I did recommend reading the paper and try with the hyperparameters that others have selected.
This is also the crucial stage in MLOps. You deploy your model to be used by the people, or you deploy your model in production.
After deployment, you monitor your system and you maintain your system.
Eg:- After deployment, let’s say you have deployed a credit card fraud detection system, then it might be that hackers change their strategy, so that system will fail, so you have to continuously monitor and maintain your system. In that case, you will retrain your model with other data.
Below I have listed one deployment pattern that if often used in the industry
Canary Deployment:– In this deployment pattern, you roll out a small percentage of traffic to your system, and then you monitor it, if all good then you go further or you come back again to tune your model.
Deployment is a very Iterative process, so don’t get offended in this case, try to ask some people who are experienced with respect to your problem.
In MLOps, Monitoring is one of the important stages. You monitor your system, how well it is performing when the traffic is coming?
Eg:- Fraction of Non-Null Outputs from the model, may happen that your model is printing nothing.
Eg:- Fraction of Input Missing Values
You can set up some metrics or alerts like Input metrics, Output metrics, etc.
Suggestions on setting up monitoring metrics:-
ML Model development is an iterative process, so is deployment.
Thanks for reading!
I hope that you’ll implement these concepts & strategies into your ML product Or Project.
Something not mentioned or want to share your thoughts? Feel free to comment below And I’ll get back to you.
Ayush Singh
I am a 14-year-old learner and machine learning and deep learning practitioner, Working in the domain of Natural Language Processing, Generative Adversarial Networks, and Computer Vision. Also, make videos on machine learning, deep learning, Gans on my youtube channel Newera. I am also a competitive coder but still practicing all the techs and a passionate learner and educator.
You can connect me on Linkedin:- Ayush Singh
Your suggestions and doubts are welcomed here in the comment section. Thank you for reading my article!
The media shown in this article are not owned by Analytics Vidhya and are used at the Author’s discretion.
8 Ways to Improve Accuracy of Machine Learning ...
A Comprehensive Guide on MLOps for Machine Lear...
MLOps Part 1: Revealing the Approach behind MLOps
MLOps – 5 Steps you Need to Know to Imple...
c Part 3: Model Deployment and Model Monitoring
MLOPs Operations: A Beginner’s Guide in P...
Creating a Robust MLOps Model for Your Organiza...
MLOps- A Process of Streamlining Organizationa...
LLMOPS vs MLOPS: Choosing the Best Path for AI ...
MLOps – Operationalizing Machine Learning Mod...
We use cookies essential for this site to function well. Please click to help us improve its usefulness with additional cookies. Learn about our use of cookies in our Privacy Policy & Cookies Policy.
Show details
This site uses cookies to ensure that you get the best experience possible. To learn more about how we use cookies, please refer to our Privacy Policy & Cookies Policy.
It is needed for personalizing the website.
Expiry: Session
Type: HTTP
This cookie is used to prevent Cross-site request forgery (often abbreviated as CSRF) attacks of the website
Expiry: Session
Type: HTTPS
Preserves the login/logout state of users across the whole site.
Expiry: Session
Type: HTTPS
Preserves users' states across page requests.
Expiry: Session
Type: HTTPS
Google One-Tap login adds this g_state cookie to set the user status on how they interact with the One-Tap modal.
Expiry: 365 days
Type: HTTP
Used by Microsoft Clarity, to store and track visits across websites.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Persists the Clarity User ID and preferences, unique to that site, on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Connects multiple page views by a user into a single Clarity session recording.
Expiry: 1 Day
Type: HTTP
Collects user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Years
Type: HTTP
Use to measure the use of the website for internal analytics
Expiry: 1 Years
Type: HTTP
The cookie is set by embedded Microsoft Clarity scripts. The purpose of this cookie is for heatmap and session recording.
Expiry: 1 Year
Type: HTTP
Collected user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Months
Type: HTTP
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected includes the number of visitors, the source where they have come from, and the pages visited in an anonymous form.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics, to store and count pageviews.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit.
Expiry: 1 Day
Type: HTTP
Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels.
Expiry: Session
Type: PIXEL
cookies ensure that requests within a browsing session are made by the user, and not by other sites.
Expiry: 6 Months
Type: HTTP
use the cookie when customers want to make a referral from their gmail contacts; it helps auth the gmail account.
Expiry: 2 Years
Type: HTTP
This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor's browser supports cookies.
Expiry: 1 Year
Type: HTTP
this is used to send push notification using webengage.
Expiry: 1 Year
Type: HTTP
used by webenage to track auth of webenagage.
Expiry: Session
Type: HTTP
Linkedin sets this cookie to registers statistical data on users' behavior on the website for internal analytics.
Expiry: 1 Day
Type: HTTP
Use to maintain an anonymous user session by the server.
Expiry: 1 Year
Type: HTTP
Used as part of the LinkedIn Remember Me feature and is set when a user clicks Remember Me on the device to make it easier for him or her to sign in to that device.
Expiry: 1 Year
Type: HTTP
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Used to store information about the time a sync with the AnalyticsSyncHistory cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Cookie used for Sign-in with Linkedin and/or to allow for the Linkedin follow feature.
Expiry: 6 Months
Type: HTTP
allow for the Linkedin follow feature.
Expiry: 1 Year
Type: HTTP
often used to identify you, including your name, interests, and previous activity.
Expiry: 2 Months
Type: HTTP
Tracks the time that the previous page took to load
Expiry: Session
Type: HTTP
Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings
Expiry: Session
Type: HTTP
Tracks percent of page viewed
Expiry: Session
Type: HTTP
Indicates the start of a session for Adobe Experience Cloud
Expiry: Session
Type: HTTP
Provides page name value (URL) for use by Adobe Analytics
Expiry: Session
Type: HTTP
Used to retain and fetch time since last visit in Adobe Analytics
Expiry: 6 Months
Type: HTTP
Remembers a user's display preference/theme setting
Expiry: 6 Months
Type: HTTP
Remembers which users have updated their display / theme preferences
Expiry: 6 Months
Type: HTTP
Used by Google Adsense, to store and track conversions.
Expiry: 3 Months
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 6 Hours
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 1 Month
Type: HTTP
These cookies are used to gather website statistics, and track conversion rates.
Expiry: 1 Month
Type: HTTP
Aggregate analysis of website visitors
Expiry: 6 Months
Type: HTTP
This cookie is set by Facebook to deliver advertisements when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.
Expiry: 4 Months
Type: HTTP
Contains a unique browser and user ID, used for targeted advertising.
Expiry: 2 Months
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 1 Year
Type: HTTP
Used by LinkedIn for tracking the use of embedded services.
Expiry: 1 Day
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 6 Months
Type: HTTP
Use these cookies to assign a unique ID when users visit a website.
Expiry: 6 Months
Type: HTTP
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
Expiry: 6 Months
Type: HTTP
Used to make a probabilistic match of a user's identity outside the Designated Countries
Expiry: 90 Days
Type: HTTP
Used to collect information for analytics purposes.
Expiry: 1 year
Type: HTTP
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
Expiry: 1 Day
Type: HTTP
Cookie declaration last updated on 24/03/2023 by Analytics Vidhya.
Cookies are small text files that can be used by websites to make a user's experience more efficient. The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies, we need your permission. This site uses different types of cookies. Some cookies are placed by third-party services that appear on our pages. Learn more about who we are, how you can contact us, and how we process personal data in our Privacy Policy.
Edit
Resend OTP
Resend OTP in 45s