feast
by
feast-dev

Description: The Open Source Feature Store for AI/ML

View on GitHub ↗

Summary Information

Updated 31 minutes ago
Added to GitGenius on June 18th, 2024
Created on December 10th, 2018
Open Issues & Pull Requests: 390 (+0)
Number of forks: 1,359
Total Stargazers: 7,127 (+0)
Total Subscribers: 88 (+0)

Issue Activity (beta)

Open issues: 212
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 345 days
Stale 30+ days: 198
Stale 90+ days: 181

Recent activity

Opened in 7 days: 2
Closed in 7 days: 0
Comments in 7 days: 5
Events in 7 days: 12

Top labels

  • kind/bug (750)
  • priority/p2 (699)
  • kind/feature (545)
  • wontfix (487)
  • good first issue (135)
  • priority/p1 (100)
  • Community Contribution Needed (69)
  • keep-open (56)

Repository Insights (GitGenius)

Median issue/PR response: 0.0 hours
Mean response time: 274.9 days
90th percentile: 1232.7 days
Tracked items: 811

Most active contributors

Detailed Description

Feast is an open source feature store designed to help machine learning platform teams productionize analytic data for both model training and online inference. Written primarily in Python, the project provides a unified data access layer that abstracts feature storage from feature retrieval, allowing organizations to manage existing infrastructure without building custom solutions. The core value proposition centers on three key capabilities: maintaining consistent features across training and serving environments through offline stores for batch processing and online stores for low-latency access, preventing data leakage through point-in-time correct feature sets, and decoupling machine learning systems from underlying data infrastructure to ensure model portability across different platforms and deployment scenarios.

The architecture documented in the repository demonstrates a minimal Feast deployment pattern, with support for expanded configurations across major cloud platforms including Snowflake, Google Cloud Platform, and Amazon Web Services. The feature store manages both offline and online data paths, with a battle-tested feature server component responsible for serving pre-computed features in real-time prediction scenarios. The project includes a web UI for exploring feature data, though this component is marked as experimental in the documentation.

The repository shows substantial development activity with 811 tracked issues and pull requests. The most frequently labeled issue categories are kind/feature with 317 items, kind/bug with 304 items, and priority/p2 with 302 items, indicating active feature development alongside bug fixes and prioritized work. Response latency metrics show a median of 0.0 hours with a mean of 6598.1 hours across these items, reflecting the project's handling of both urgent and longer-term work. The primary contributors driving development include franciscojavierarceo with 709 recorded events, tokoko with 285 events, and ntkathole with 257 events, demonstrating concentrated but distributed leadership in the project's evolution.

The repository's classification spans multiple machine learning and data engineering domains including real-time inference, ML pipeline integration, event streaming, feature serving, data governance, and MLOps. This breadth reflects Feast's positioning as a comprehensive platform addressing the full lifecycle of feature management from data transformation through model serving. The project maintains connections to other major open source ecosystems, with GitGenius identifying overlapping contributors with microsoft/vscode, microsoft/typescript, and rust-lang/rust, suggesting cross-pollination of ideas and practices from adjacent development communities.

Feast's functionality roadmap explicitly welcomes community contributions across all planned items, indicating an open development model. The getting started documentation guides users through installation, feature repository creation, feature definition registration, data exploration, training dataset construction, materialization options, and online feature retrieval. The materialization process offers multiple strategies including incremental materialization, full materialization with timestamps, and simple materialization without timestamps, providing flexibility for different data source characteristics and operational requirements. This design acknowledges that real-world data infrastructure varies significantly in timestamp availability and update patterns.

feast
by
feast-devfeast-dev/feast

Repository Details

Fetching additional details & charts...