LogoLogo
v0.23-branch
masterv0.11-branchv0.12-branchv0.13-branchv0.14-branchv0.15-branchv0.16-branchv0.17-branchv0.18-branchv0.19-branchv0.20-branchv0.21-branchv0.22-branchv0.23-branchv0.24-branchv0.25-branchv0.26-branchv0.27-branchv0.28-branchv0.29-branchv0.30-branchv0.31-branchv0.34-branchv0.35-branchv0.36-branchv0.37-branchv0.38-branchv0.39-branchv0.40-branchv0.41-branchv0.42-branchv0.43-branchv0.45-branchv0.45-branchv0.46-branchv0.47-branchv0.48-branch
v0.23-branch
masterv0.11-branchv0.12-branchv0.13-branchv0.14-branchv0.15-branchv0.16-branchv0.17-branchv0.18-branchv0.19-branchv0.20-branchv0.21-branchv0.22-branchv0.23-branchv0.24-branchv0.25-branchv0.26-branchv0.27-branchv0.28-branchv0.29-branchv0.30-branchv0.31-branchv0.34-branchv0.35-branchv0.36-branchv0.37-branchv0.38-branchv0.39-branchv0.40-branchv0.41-branchv0.42-branchv0.43-branchv0.45-branchv0.45-branchv0.46-branchv0.47-branchv0.48-branch
  • Introduction
  • Community
  • Roadmap
  • Changelog
  • Getting started
    • Quickstart
    • Concepts
      • Overview
      • Data ingestion
      • Entity
      • Feature view
      • Feature retrieval
      • Point-in-time joins
      • Registry
      • [Alpha] Saved dataset
    • Architecture
      • Overview
      • Registry
      • Offline store
      • Online store
      • Batch Materialization Engine
      • Provider
    • Learning by example
    • Third party integrations
    • FAQ
  • Tutorials
    • Sample use-case tutorials
      • Driver ranking
      • Fraud detection on GCP
      • Real-time credit scoring on AWS
      • Driver stats on Snowflake
    • Validating historical features with Great Expectations
    • Using Scalable Registry
    • Building streaming features
  • How-to Guides
    • Running Feast with Snowflake/GCP/AWS
      • Install Feast
      • Create a feature repository
      • Deploy a feature store
      • Build a training dataset
      • Load data into the online store
      • Read features from the online store
    • Running Feast in production
    • Upgrading for Feast 0.20+
    • Customizing Feast
      • Adding a custom batch materialization engine
      • Adding a new offline store
      • Adding a new online store
      • Adding a custom provider
    • Adding or reusing tests
  • Reference
    • Codebase Structure
    • Data sources
      • File
      • Snowflake
      • BigQuery
      • Redshift
      • Push
      • Kafka
      • Kinesis
      • Spark (contrib)
      • PostgreSQL (contrib)
      • Trino (contrib)
    • Offline stores
      • Overview
      • File
      • Snowflake
      • BigQuery
      • Redshift
      • Spark (contrib)
      • PostgreSQL (contrib)
      • Trino (contrib)
    • Online stores
      • SQLite
      • Snowflake
      • Redis
      • Datastore
      • DynamoDB
      • PostgreSQL (contrib)
    • Providers
      • Local
      • Google Cloud Platform
      • Amazon Web Services
    • Feature repository
      • feature_store.yaml
      • .feastignore
    • Feature servers
      • Python feature server
      • [Alpha] Go feature server
      • [Alpha] AWS Lambda feature server
    • [Beta] Web UI
    • [Alpha] On demand feature view
    • [Alpha] Data quality monitoring
    • Feast CLI reference
    • Python API reference
    • Usage
  • Project
    • Contribution process
    • Development guide
      • Maintainer Docs
    • Versioning policy
    • Release process
    • Feast 0.9 vs Feast 0.10+
Powered by GitBook
On this page
  1. Getting started
  2. Architecture

Online store

PreviousOffline storeNextBatch Materialization Engine

Last updated 2 years ago

The Feast online store is used for low-latency online feature value lookups. Feature values are loaded into the online store from data sources in feature views using the materialize command.

The storage schema of features within the online store mirrors that of the data source used to populate the online store. One key difference between the online store and data sources is that only the latest feature values are stored per entity key. No historical values are stored.

Example batch data source

Once the above data source is materialized into Feast (using feast materialize), the feature values will be stored as follows:

Features can also be written to the online store via

push sources