# Feature Store Backend Decision

## Decision

Use Feast as the optional interoperability backend while retaining the native
Redis/PostgreSQL stores as the default Oshun runtime. The integration targets
Feast's language-neutral feature-server endpoints for online retrieval, push,
and dual online/offline writes.

## Rationale

Feast is open source, can be self-hosted, exposes point-in-time historical
retrieval and online materialization primitives, and has a documented HTTP
feature server. Those properties match Oshun's sovereignty and mixed-language
requirements. Tecton provides a strong managed control plane and transformation
workflow, but adopting it as the required backend would introduce a proprietary
service dependency and recurring platform coupling.

## Integration Boundary

`FeastFeatureServerClient` implements authenticated JSON requests for
`/get-online-features` and `/push`, including `online_and_offline` writes. The
native stores remain responsible for low-latency Redis serving and PostgreSQL
point-in-time history when Feast is not deployed. Feature definitions and access
policies remain in `FeatureCatalog`, so switching serving backends does not move
domain ownership or authorization policy into an external system.

## Revisit Criteria

Re-evaluate Tecton if managed scheduling, transformation observability, and
operational support demonstrably offset sovereignty, cost, and portability
tradeoffs. Re-evaluate the native store if Feast becomes the standard runtime
for every deployment and matches the native latency and lineage gates.
