Architecture Decision Records

This directory contains Architecture Decision Records (ADRs) for the Feast project. ADRs document significant architectural decisions made during the development of Feast, providing context, rationale, and consequences for each decision.

What is an ADR?

An Architecture Decision Record captures a single architectural decision, including the context in which it was made, the decision itself, and the expected consequences. ADRs serve as a historical record for current and future contributors to understand why the project is structured the way it is.

ADR Index

ADR	Title	Status	Original RFC
ADR-0001	Feature Services	Accepted	RFC-015
ADR-0002	Component Refactor	Accepted	RFC-020
ADR-0003	On-Demand Transformations	Accepted	RFC-021
ADR-0004	Entity Join Key Mapping	Accepted	RFC-023
ADR-0005	Stream Transformations	Accepted	RFC-036
ADR-0006	Kubernetes Operator	Accepted	RFC-042
ADR-0007	Unified Feature Transformations and Feature Views	Accepted	RFC-043
ADR-0008	Feature View Versioning	Accepted	Feature View Versioning RFC
ADR-0009	Contribution and Extensibility Architecture	Accepted	RFC-014
ADR-0010	Vector Database Integration for LLM/RAG Support	Accepted	RFC-040
ADR-0011	Data Quality Monitoring	Accepted	RFC-027

Creating a New ADR

1. Copy the ADR template to a new file with the next sequential number.

2. Fill in all sections of the template.

3. Submit a pull request with the new ADR.

4. Once the RFC is finalized and approved, update the ADR status to "Accepted".

ADR Statuses

• Proposed: The decision is under discussion.

• Accepted: The decision has been accepted and is being (or has been) implemented.

• Deprecated: The decision is no longer relevant due to changes in the project.

• Superseded: The decision has been replaced by a newer ADR.