Feature Store

Full definition

A feature store provides two interfaces: an offline store (columnar warehouse) for training and batch scoring, and an online store (low-latency key-value DB) for real-time inference. Both are populated from the same feature pipelines, eliminating training-serving skew — a leading cause of production model failure. Uber introduced the pattern with Michelangelo (2017); modern implementations include the open-source Feast and the commercial Tecton platform, which agreed in 2025 to join Databricks. AIDOLS uses a feature store as the backbone of every production ML platform it delivers.

Why it matters

Without a feature store, every team rebuilds feature logic in Python notebooks, then again in production code, then again in monitoring. Bugs emerge silently as offline and online definitions diverge. A feature store collapses that fan-out into one source of truth and is correlated with materially shorter time-to-production for new models.

Example

A fintech defines "user_avg_transaction_value_30d" once in the feature store. Training jobs pull historical values; the fraud model in production reads the same feature at sub-10ms latency through the online store.

Next steps

• Get a free workflow map →We map one of your workflows and give you a written verdict: software, a process change or AI. No obligation.
• AI consulting cost guide →Hourly rates and project budgets by firm tier, from independents to the Big Four.

Related terms

• MLOps
  MLOps is the discipline of operating machine-learning and AI systems reliably in production — covering data pipelines, model training, deployment, monitoring, drift detection, governance, and incident response — analogous to DevOps for traditional software.
• Model Serving
  Model serving is the runtime infrastructure that hosts a trained model and exposes it as an API for low-latency online inference at scale, handling batching, autoscaling, GPU sharing, versioning, and routing.
• Online Inference
  Online inference returns model predictions synchronously in response to a live user or system request, within an interactive latency budget.
• Model Monitoring
  Model monitoring is the continuous measurement of a deployed model's inputs, outputs, and performance signals — including data drift, prediction drift, label drift, latency, and ground-truth accuracy — to detect degradation before it harms business outcomes.

More deployment & operations terms

• Model Registry
  A model registry is a versioned catalog that tracks every trained ML model artifact, along with its metadata, training data lineage, evaluation metrics, approval status, and deployment stage (staging, production, archived).
• A/B Testing for ML
  A/B testing for ML is the practice of randomly splitting live traffic between a control model and a candidate model to measure the candidate's causal impact on real business metrics — revenue, conversion, retention, defect rate.
• Canary Deployment
  A canary deployment routes a small slice of production traffic (e.g., 1–5%) to a new model version while the majority continues hitting the stable version, surfacing latency, error, and quality regressions before full rollout.