📊 Analytics & BI

Feature Store

A centralized platform for storing, managing, and serving ML features — ensuring consistency between model training and real-time inference.

A Feature Store is a centralized repository for storing, versioning, and serving machine learning features. It bridges the gap between data engineering and ML engineering by providing a single source of truth for feature definitions, ensuring that the features used during model training are identical to those used during real-time inference.

The Problem Feature Stores Solve

``
Without Feature Store:
Training: SQL query → Pandas → feature engineering → model.fit()
Serving: API request → different code → different features → SKEW!

With Feature Store:
Training: feature_store.get_historical('user_features') → model.fit()
Serving: feature_store.get_online('user_features') → model.predict()
Result: SAME features, ZERO skew
``

Training-Serving Skew


The #1 problem in ML production: features computed differently during training vs. inference, causing model performance degradation.

Core Components

Offline Store


- Purpose: Store historical feature values for model training
- Storage: Data warehouse (Snowflake, BigQuery) or data lake (S3 + Iceberg)
- Access Pattern: Batch reads, point-in-time lookups
- Example: "What was this user's 30-day purchase count on March 1, 2025?"

Online Store


- Purpose: Serve latest feature values for real-time inference
- Storage: Low-latency databases (Redis, DynamoDB, Bigtable)
- Access Pattern: Single-key lookups in <10ms
- Example: "What is this user's current session count right now?"

Feature Registry


- Purpose: Catalog and document all features
- Contains: Feature definitions, owners, data types, descriptions
- Enables: Feature discovery and reuse across teams

Popular Feature Stores

| Tool | Type | Best For |
|------|------|----------|
| Feast | Open Source | Simple, flexible, Kubernetes-native |
| Tecton | Managed | Enterprise real-time ML |
| Databricks Feature Store | Integrated | Databricks/MLflow users |
| SageMaker Feature Store | Managed | AWS-native ML workflows |
| Hopsworks | Open Source | Feature pipelines + serving |
| Snowflake (Cortex) | Integrated | Snowflake-native ML |

Use Cases

1. Fraud Detection: Real-time features (transaction velocity, device fingerprint)
2. Recommendations: User behavior features served in <10ms
3. Credit Scoring: Consistent features across training and scoring
4. Search Ranking: Real-time query + user features for personalization
5. Dynamic Pricing: Market signals as features for pricing models

Key Points

Frequently Asked Questions

What is a feature store in machine learning?

A feature store is a centralized platform that stores, manages, and serves ML features. It ensures the same feature definitions and computations are used during both model training and real-time prediction, preventing training-serving skew.

Why do you need a feature store?

Without a feature store, teams often compute features differently during training vs. serving, causing model degradation. A feature store provides a single source of truth, enables feature reuse across teams, and handles both batch and real-time serving.

What is the difference between offline and online feature stores?

The offline store holds historical feature values for batch model training. The online store holds the latest feature values for real-time inference (<10ms latency). A feature store typically syncs data between both.

← Back to Glossary

Last updated: 2026-02-27

SR

Published by

Sainath Reddy

Data Engineer at Anblicks
🎯 4+ years experience