Feature Stores with Feast
A feature store organizes and serves the input data that machine-learning models use. Feast connects existing batch and online data systems so the same named features can support historical training and live inference.
itArtificial intelligence and machine learning | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Intro
Feature Stores with Feast
A feature is a value supplied to a machine-learning model, such as a driver's completed trips in the last hour. A feature store gives those values shared definitions and retrieval paths. Feast is an open-source feature store that connects existing data infrastructure to model training and inference.
The central problem is time. Training needs historical values as they were known at each labeled event. Online inference usually needs the latest values for one or more entity keys. Building those paths separately can produce training-serving skew: the model trains on values created or joined differently from the values it receives in production.
Architecture and data flow
Feast separates feature definitions from feature data. A feature repository contains Python definitions and a feature_store.yaml configuration. Running feast apply validates those definitions, updates the registry, and may configure provider resources.
The main objects are:
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://feast.dev/
Supports
- Feast as an open-source feature store for training and inference
- Supported offline and online integration categories
- Feast product-landscape placement and official URL
- https://docs.feast.dev/getting-started/introduction
Supports
- Feast scope for defining, managing, validating, and serving features
- Roles for data scientists, data engineers, MLOps engineers, and AI engineers
- Reference-path rationale for the official introduction
- https://docs.feast.dev/getting-started/quickstart
Supports
- Local repository, apply, historical retrieval, materialization, and online retrieval flow
- Local provider defaults and model-facing SDK examples
- Reference-path rationale for the maintained quickstart
- https://docs.feast.dev/getting-started/components/overview
Supports
- Batch and stream feature creation outside and alongside Feast
- feast apply updating infrastructure and registry definitions
- Materialization from offline to online storage
- Point-in-time historical retrieval for training
- Quiz answers about materialization and stale values
- https://docs.feast.dev/getting-started/concepts/entity
Supports
- Entities as semantic subjects associated with feature views
- Join keys as physical keys used during retrieval
- Quiz answer about entity responsibility
- https://docs.feast.dev/getting-started/concepts/feature-view
Supports
- Feature views as groups of fields with sources, entities, schemas, metadata, and TTL
- Use in historical retrieval, materialization, and online retrieval
- Timestamp requirement and TTL behavior
- On-demand transformation behavior and offline scaling limitation
- https://docs.feast.dev/getting-started/concepts/feature-service
Supports
- Feature services as logical selections across feature views
- Model-oriented grouping for historical and online retrieval
- Applying a feature service does not deploy a network service
- Quiz answers about feature-service behavior
- https://docs.feast.dev/getting-started/concepts/feature-retrieval
Supports
- Entity dataframes containing join keys and event timestamps
- Point-in-time historical joins excluding future feature values
- Online retrieval by entity rows and feature references
- Quiz answers about temporal selection, timestamps, and TTL
- https://docs.feast.dev/getting-started/components/registry
Supports
- Registry as central catalog for feature definitions and metadata
- Registry updates through feast apply
- Local and remote registry deployment roles
- Quiz answer distinguishing metadata from feature values
- https://docs.feast.dev/reference/offline-stores/overview
Supports
- Offline-store interfaces for point-in-time joins and materialization reads
- Provider capability differences
- Reference-path rationale for comparing offline engines
- https://docs.feast.dev/getting-started/components/online-store
Supports
- Online stores serving low-latency features
- Materialization loading values into the online store
- Latest value per entity key and absence of historical values online
- Quiz answers about online freshness
- https://docs.feast.dev/reference/online-stores
Supports
- Multiple supported online-store implementations
- Reference-path rationale for backend comparison
- https://docs.feast.dev/reference/data-sources/push
Supports
- Push sources writing fresh values online and optionally offline
- Push modes and batch-source relationship
- Quiz answer about second-level freshness
- https://docs.feast.dev/getting-started/architecture/push-vs-pull-model
Supports
- Push model as read-optimized low-latency design
- Strong consistency requiring explicit surrounding design
- Tradeoff between request-time pulls and prewritten values
- https://docs.feast.dev/how-to-guides/running-feast-in-production
Supports
- Production use of remote registries, materialization jobs, and feature servers
- Reference-path rationale for deployment study
- https://github.com/feast-dev/feast
Supports
- Apache-2.0 licensing
- Maintained source, examples, changelog, and contribution material
- Reference-path rationale for release-specific behavior
- https://github.com/feast-dev/feast/blob/master/docs/getting-started/faq.md
Supports
- Feature-service-per-model versioning guidance
- Feature views used by services treated as immutable contracts
- Quiz answer about versioned rollout
- https://feast.dev/blog/future-of-feast/
Supports
- Feast started in 2018 and was open sourced in late 2018
- Feast entered the Linux Foundation for AI in 2020
- Timeline research decision and lack of a sufficiently granular milestone arc in the project retrospective
- https://github.com/feast-dev/feast/blob/master/CHANGELOG.md
Supports
- Release-level history reviewed for the timeline applicability decision
- Decision not to pad a milestone timeline with routine release entries
- https://github.com/sindresorhus/awesome
Supports
- Discovery route to curated engineering and MLOps lists
- https://github.com/kelvins/awesome-mlops
Supports
- Discovery of Feathr, Featureform, Butterfree, and ByteHub as feature-store ecosystem projects
- https://feathr-ai.github.io/feathr/docs/concepts
Supports
- Feathr transformation, point-in-time, registry, and materialization concepts
- Feathr Awesome Link rationale and landscape placement
- https://docs.featureform.com/getting-started/architecture-and-components
Supports
- Virtual feature-store architecture over pluggable providers
- Feature definitions, training sets, transformations, and inference serving
- Featureform Awesome Link rationale and landscape placement
- https://butterfree.readthedocs.io/en/latest/home.html
Supports
- ETL stages for producing historical and online feature-store outputs
- Butterfree Awesome Link rationale
- https://bytehub-ai.github.io/bytehub/bytehub/
Supports
- Time-series-focused feature-store API
- ByteHub Awesome Link rationale
- https://docs.hopsworks.ai/latest/concepts/fs/
Supports
- Hopsworks feature groups, feature views, offline and online APIs, and point-in-time joins
- Hopsworks landscape placement
- https://docs.tecton.ai/docs/introduction
Supports
- Managed batch, streaming, real-time, offline, and online feature lifecycle
- Tecton landscape placement
- https://docs.aws.amazon.com/sagemaker/latest/dg/feature-store.html
Supports
- SageMaker online and offline feature groups
- Batch and streaming ingestion, historical storage, and low-latency lookup
- SageMaker Feature Store landscape placement
- https://cloud.google.com/vertex-ai/docs/featurestore
Supports
- Vertex AI Feature Store managing and serving feature data from BigQuery
- Feature views and managed online serving
- Vertex AI Feature Store landscape placement
- https://docs.databricks.com/aws/en/machine-learning/feature-store/concepts
Supports
- Unity Catalog feature tables, model lineage, feature lookup, batch and online serving
- Databricks Feature Store landscape placement
- https://docs.snowflake.com/en/developer-guide/snowflake-ml/feature-store/overview
Supports
- Feature stores as schemas and feature views as dynamic tables or views
- Scheduled refresh, point-in-time retrieval, transformations, governance, and lineage
- Snowflake Feature Store landscape placement
- https://learn.microsoft.com/en-us/azure/machine-learning/concept-what-is-managed-feature-store?view=azureml-api-2
Supports
- Versioned feature sets, managed Spark materialization, backfill, offline retrieval, and online serving
- Azure Machine Learning managed feature store landscape placement
