Feature Stores: Overhyped or Underused?
Everyone has an opinion on feature stores. Most of them are wrong. Here's when you actually need one.
The feature store debate follows a predictable arc.
First, someone hypes it as the solution to all your ML problems. Then someone else writes a post about how they threw theirs out and everything got simpler. Then everyone has a hot take and nothing gets shipped.
Here’s the actual answer: a feature store is a forcing function. Whether you need the forcing function depends on where you are.
You probably don’t need a feature store if:
You’re running one or two models in production with a handful of features per model. Your data team is small, your feature definitions are stable, and the same team builds models and pipelines. Congratulations — your mental model is your feature store.
You absolutely need one if:
Multiple teams are computing the same features independently. You’ve had an incident where the training pipeline and the serving pipeline disagreed on what “7-day rolling average” means. Your models are degrading and you can’t tell if it’s data drift, a pipeline bug, or both.
That last scenario is the real tell. Training-serving skew is silent until it isn’t. By the time you notice it in production metrics, you’ve already made bad decisions based on a model that was never evaluating what you thought it was.
A feature store solves this by making feature definitions a first-class artifact — versioned, tested, shared. Features become something you deploy, not something you copy-paste into a notebook and hope for the best.
The underuse problem is real
Most teams wait too long to adopt one. They hit pain first — skew incidents, duplicate logic, debugging nightmares — then scramble to retrofit a feature store into a production system that wasn’t designed for it. Retrofits are never fun.
The right time to introduce a feature store is before you have three teams or more than 20 features. Not after.
Pick Feast if you want open-source flexibility. Pick Tecton or Hopsworks if you want managed with SLAs. Pick nothing if you genuinely don’t need it yet.
But don’t confuse simplicity now with simplicity later. The teams that skip this infrastructure don’t avoid the problem — they defer it to the worst possible moment.
Feature stores aren’t hype. They’re insurance. And like most insurance, you only regret not having it after the incident.