---
title: "Feature Store"
description: "2 posts about Feature Store, summarised, each linking to the original."
---

# Feature Store
> 2 posts about Feature Store, summarised, each linking to the original.

## Articles

### [Build a real-time next-best-offer recommender using Databricks Feature Views](https://yomu.fyi/post/build-a-real-time-next-best-offer-recommender-using-databricks-feature.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Tian Tan, Sixuan He, Nick Joung, Julia Powell
- Published: Nov 16, 2026
- Type: Tutorial

Real-time personalization in retail banking requires aggregating clickstream data into time-windowed features for both training and serving, but separate pipelines create duplicate definitions that can drift. Databricks Feature Views solve this by letting you define features once for point-in-time-correct training and low-latency online serving. The open-source Solution Accelerator builds a next-best-offer recommender that ranks offers like credit card upgrades and personal loans using a LightGBM ranker. Streaming features from Kafka are continuously aggregated into the online store using RollingWindow and SawtoothWindow declarations, eliminating separate hand-written streaming jobs. In benchmarks, the ranking endpoint achieved 34 ms p95 latency and sustained approximately 56 requests per second on the smallest configuration.


### [Real-time fraud detection with Feature Views](https://yomu.fyi/post/real-time-fraud-detection-with-feature-views.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Shyam Sankararaman, Hedvig Vahlberg
- Published: Nov 6, 2026
- Type: Tutorial

Real-time fraud detection needs three feature types: recent activity (e.g., five-minute transaction count), spending baselines (30-day average and standard deviation), and current payment details. Databricks Feature Views address this by defining each feature once for both training and serving, producing point-in-time correct training data and online inference pipelines. The walkthrough follows a $900 payment from a Kafka stream through RollingWindow and SawtoothWindow aggregations to a fraud score from Model Serving. Feature Views prevent training-serving skew and data leakage; on-demand features compare the current amount against stored baselines at request time. Unity Catalog governs definitions, permissions, and lineage, while MLflow records model dependencies and Model Serving retrieves features from the Online Feature Store.
