Welcome to this third article in my MLOps collection. In the primary article, we explored Docker and the way it simplifies utility packaging. In the second article, we managed machine studying fashions utilizing MLflow, Azure, and Docker. Now, on this third half, we’ll deliver all the things collectively by constructing a FastAPI utility that serves our beforehand saved mannequin on Azure. This enables us to create a prediction service that may be accessed globally!
An API is sort of a bridge. Everytime you work together with a library in Python, you’re utilizing its API. It’s the general public a part of an utility that you could work together with, whereas all the things behind it’s hidden.
APIs are generally used to speak with internet purposes, and so they present a set of URLs that return knowledge (You ship a request with some parameters and get a response again). Most frequently, the information comes again in codecs like JSON or XML, that are straightforward to parse. That is totally different from web sites that return HTML, which incorporates information for rendering pages. With APIs, you get simply the uncooked knowledge.
Some APIs are public, whereas others are personal. When constructing an API, you determine what knowledge to share, the right way to…