article thumbnail

MLOps Is an Extension of DevOps. Not a Fork — My Thoughts on THE MLOPS Paper as an MLOps Startup CEO

The MLOps Blog

Most of our customers are doing ML/MLOps at a reasonable scale, NOT at the hyperscale of big-tech FAANG companies. Not a fork: – The MLOps team should consist of a DevOps engineer, a backend software engineer, a data scientist, + regular software folks. How about the ML engineer? Let me explain.

DevOps 59
article thumbnail

MLOps Landscape in 2023: Top Tools and Platforms

The MLOps Blog

Can you see the complete model lineage with data/models/experiments used downstream? Some of its features include a data labeling workforce, annotation workflows, active learning and auto-labeling, scalability and infrastructure, and so on. MLOps workflows for computer vision and ML teams Use-case-centric annotations.

article thumbnail

Deploying Conversational AI Products to Production With Jason Flaks

The MLOps Blog

You have a bit of education in music composition, math, and science before you get more into the software engineering side of things. But you have started out in software design engineering, is that correct? But it’s absolutely critical for most people in our space that you do some type of auto-scaling.