May we use cookies so Meta, Google, LinkedIn and ChatGPT see your visit and we learn which ads work? PrivacyMay we use cookies to see which pages help, and let Meta, Google, LinkedIn and ChatGPT see your visit, so we know which of our ads work? That way we spend less on ads that do not work. We do not sell your data, and the site works the same if you decline. You can change your answer at any time under Cookie settings at the foot of the page. Privacy policy
Loading...
AI Engineering · Features And Feature Stores
Free preview: the first 2 parts of this 28-part lesson.
Already bought the course? Sign in to read the whole lesson.
this lesson is part of
Generative AI and Agentic AI Engineering
Unlock this lesson and the 208 other paid lessons
$35 once, by card or PayPal
See the Generative AI and Agentic AI courseread the rest of this lesson in
Generative AI and Agentic AI Engineering
Unlock this lesson and the 208 other paid lessons
$35 once, by card or PayPal
See the Generative AI and Agentic AI coursein Features And Feature Stores
This lesson is part of the AI Engineering course. Unlock the full course, a separate one-time payment, for lifetime access.
One-time payment by card or PayPal
Get Lifetime AccessOne-time payment: UPI, card or netbanking
Get Lifetime AccessFoundation lessons of this course are free, no payment needed. Try them now
Let me start with a notebook and a library.
Imagine you help at a small club. For a year, you keep every member's record in your own notebook. Each night you write a new line for anyone who did something that day. The line says how many times they have visited so far, and how much they have paid so far. You date each line with the next morning, because that is when the line is finished.
When someone asks "how active was this member on 1 July?", you do not read the newest line. You turn back to the last line dated on or before 1 July. That way you never use what happened later.

Now a real library offers to keep the records for you. It has a proper catalogue, rules and staff. It says it can answer the same question for thousands of members at once. Before you hand over your notebook, you would want to check one thing. Does the library give the same answer as your notebook, for every member and every date? And are there any library rules you did not know about?
I do exactly this in this lesson. My notebook is the code I wrote in lessons 1 and 2. The library is a real called Feast.
This is the last lesson of the chapter, so it leans on the earlier ones. If the shop, the customers or the question are new, please read what a feature is first. That lesson built six features from each customer's history: recency, frequency, money, return share, tenure and products. The question is always the same. At the start of a month, will this customer buy something in the next 30 days?
The most important earlier lesson here is point-in-time joins. It showed that joining each customer's latest values promised a score of 0.714 and delivered 0.301, and it wrote the correct join by hand with pandas' merge_asof. In this lesson I hand the same job to Feast and compare the two, row by row.
Three more lessons come back here. Feature freshness described how a copies values to a fast store. Online and offline consistency compared two programs that compute the same feature. Missing at serving read in Feast's source code what happens to a customer the store does not know. Here I run it.
The survey lesson feature stores explains what a feature store is and why teams use one. I do not repeat it. This lesson only measures.