Feature server
The Feature Server is a core architectural component in Feast, designed to provide low-latency feature retrieval and updates for machine learning applications.
It is a REST API server built using FastAPI and exposes a limited set of endpoints to serve features, push data, and support materialization operations. The server is scalable, flexible, and designed to work seamlessly with various deployment environments, including local setups and cloud-based systems.
Motivation
In machine learning workflows, real-time access to feature values is critical for enabling low-latency predictions. The Feature Server simplifies this requirement by:
Serving Features: Allowing clients to retrieve feature values for specific entities in real-time, reducing the complexity of direct interactions with the online store.
Data Integration: Providing endpoints to push feature data directly into the online or offline store, ensuring data freshness and consistency.
Scalability: Supporting horizontal scaling to handle high request volumes efficiently.
Standardized API: Exposing HTTP/JSON endpoints that integrate seamlessly with various programming languages and ML pipelines.
Secure Communication: Supporting TLS (SSL) for secure data transmission in production environments.
Architecture
The Feature Server operates as a stateless service backed by two key components:
Online Store: The primary data store used for low-latency feature retrieval.
Registry: The metadata store that defines feature sets, feature views, and their relationships to entities.
Key Features
RESTful API: Provides standardized endpoints for feature retrieval and data pushing.
CLI Integration: Easily managed through the Feast CLI with commands like
feast serve
.Flexible Deployment: Can be deployed locally, via Docker, or on Kubernetes using Helm charts.
Scalability: Designed for distributed deployments to handle large-scale workloads.
TLS Support: Ensures secure communication in production setups.
Endpoints Overview
/get-online-features
Retrieves feature values for specified entities and feature references.
/push
Pushes feature data to the online and/or offline store.
/materialize
Materializes features within a specific time range to the online store.
/materialize-incremental
Incrementally materializes features up to the current timestamp.
Last updated