Chapter 8. Deploying a GenAI Application with MLflow
In the previous chapter, we upgraded our Unity Airways assistant from a basic tool-calling agent into a more capable agent and registered it in Unity Catalog. Now that our agent is built and safely stored, it’s time to get it out into the real world where it can actually start helping users.
This chapter focuses on that next step: deployment. We will explore how MLflow manages the lifecycle of your AI application. This is where the specific components MLflow uses to deploy, govern, and version your developed agent on Databricks will shine, and help you reliably transition your application from development to a production environment.
As we operationalize our Unity Airways assistant, we’ll walk through these different steps needed for proper agent productionization (see Figure 8-1):
-
Deploying our agent to an endpoint for downstream usage
-
Setting Unity AI Gateway for endpoint access control and rate limitations
-
Adding AI guardrails to watch out for inquiries relevant to our Unity Airways assistant
-
Setting authentication methods to agents, tools, and data for production best practices
-
Using LLMOps best practices to address any challenges in production
These steps will ensure you make the right architectural decisions for your projects so that your deployments are effective, secure, and compliant.
Figure 8-1. Productionizing ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access